Error switching context with no cached connection

[driv]

Describe the bug
There is some issue with switching context (or retrying) after a failed connection.

10:38AM ERR Fail to load global/context configuration error="the server could not find the requested resource\ncannot connect to context: not_working_context\nk8s connection failed for context: not_working_context"
10:38AM ERR Load cluster resources - No API server connection
10:38AM ERR failed to list contexts error="no connection"
10:38AM WRN Unable to dial discovery API error="no connection to dial"
10:38AM ERR can't connect to cluster error="the server could not find the requested resource"
10:38AM ERR Load cluster resources - No API server connection
10:38AM WRN Unable to dial discovery API error="no connection to dial"
10:38AM ERR Context switch failed error="no connection to cached dial"
10:38AM ERR no connection to cached dial
10:39AM ERR Context switch failed error="no connection to cached dial"
10:39AM ERR no connection to cached dial
10:39AM ERR Context switch failed error="no connection to cached dial"
10:39AM ERR no connection to cached dial
In that case I retried to connect to the working context 3 times.

To Reproduce
Steps to reproduce the behavior:

k9s --context not_working_context

Try to quickly switch to any other context and the error no connection to cached dial will appear.
After the default timeout (15s) it's possible to switch context.

Historical Documents
When applicable please include any supporting artifacts: k9s debug logs, configurations, resource manifests, ...

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Versions (please complete the following information):

• OS: N/A
• K9s: v0.32.7
• K8s: N/A

Additional context
Add any other context about the problem here.