Changing Jupyter server connection requires a workspace-based session

Follow up to microsoft/vscode-python#12340, which was already closed meanwhile:

I noticed that the command “Specify local or remote Jupyter server for connections” doesn’t allow to enter a new connection: Enter is just ignored. Selecting previous servers doesn’t work either. I had to go through settings to change this config in python.dataScience.jupyterServerURI. The issue only occurs when I don’t have a workspace session opened.

@greazer answered in https://github.com/microsoft/vscode-python/issues/12340#issuecomment-644396380:

We don’t think it’s appropriate for us to set a global setting to deal with this.

I don’t really agree. If there is such a global configuration setting, why not allow editing it via the obvious command to change it? To be sure about the user’s intention, you could use a confirmation question. My key point is, that the warning notification was displayed at the other end of the screen and I didn’t notice it at all. This lead to confusion and frustration, because vscode didn’t react as expected. Please re-consider to change the behaviour here. Also, most other settings are applied globally as well if no workspace is available, aren’t they?

[DonJayamanne]

Re-assigning to Ian as this deals with the entire workflow of kernel selection UI, remote to local, etc. I believe this will all go away with the new UX that’s being worked on.

[DonJayamanne]

Closing this issue as resolved, we have a new kernel picker and remote kernel connection workflow that will be released in the next relaees (some time today /next day or so) and will be documented in the relase notes