Support switching to a context having human readable name

[vageeshabr]

Is your feature request related to a problem? Please describe.
Today if i have a context named "AKS Dev Env", switching to it fails with error •set current context failed. getcontext - invalid context specified: "Env"

Describe the solution you'd like
Allow context switching even if context name has spaces.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context

[vageeshabr]

@derailed - let me know if you think its not a good idea to have this.

[sumansuhag]

Hi Dear Sir, | Good Morning |,

Your feature request addresses a real usability problem. Supporting context names with spaces would make context management more flexible and user-friendly. Until this is implemented, consider using underscores or hyphens in context names or ensure you quote names with spaces when switching contexts, if your tool supports it.

Renaming contexts to avoid spaces .

Manually editing the kubeconfig file to change context names so they do not contain spaces.

Using quotation marks when specifying context names with spaces, if supported by the CLI.

[derailed]

@sumansuhag You are correct. K9s should be on par with kubectl and context naming should be up to the user prefs.
That said, per you usability nag, I have to disagree ku --context my-context-rocks get po vs ku --context 'my context rocks' get po would drive me absolutely off the wall when administering clusters. Hence supported != usable
Imho this actually worsen usability, to boot zero value add...
In any case, the proposed PR is suboptimal as it does not support context with spaces switching via k9s command prompt ;(

[sumansuhag]

Yes Dear Sir,
Thanks for your engagement and for maintaining such a responsive project!