Is your enhancement related to a problem? Please describe

follows up on #23558

Steps:

1. ASSERT: have a kube config (or KUBECONFIG env var with a file) which has a token configured
2. EXEC: in JetBrains Gateway click on "Connect to Dev Spaces"
3. ASSERT: you get a wizard page where there's the server url and a token. Those are filled with the content in the kube config file
4. EXEC: provide a different valid token and click "Check connection and continue"
5. ASSERT: you get to the page which lists the existing workspaces
6. EXEC: click "Back" & look at the token

Result:
The token is back to the value in the kube config, the token that you provided is gone.

Describe the solution you'd like

Allow the user to save the new token to the kube config file. Ideally it should be explicit so that changing the kube config is not unexpected. Could be achieved via ex. a checkbox "[x] Save to kube config file"

Describe alternatives you've considered

No response

Additional context

No response