Can't change remote Jupyter server without restarting VS Code

Issue Type: Bug

After one of the recent updates, I can no longer change the remote Jupyter server without restarting VS Code. I used to be able to simply comment out the remote and local Jupyter python.dataScience.jupyterServerURIs that I was not using and un-comment the one that I wanted to use and after closing the VS Code Python notebook pane everything would switch just fine. Now after changing the python.dataScience.jupyterServerURI it is only recognized after I restart VS Code.

Is there a way to get back the old behavior? It was much more convenient.

	"settings":  {
		// local
		// "python.dataScience.jupyterServerURI":  "local"
		// Remote # 1
		// "python.dataScience.jupyterServerURI": "http://100.100.100.001:8888/?token=*******************"
		// Remote # 2
		"python.dataScience.jupyterServerURI": "http://100.100.100.002:8888/?token=*******************"
	 }

Extension version: 2020.9.114305 VS Code version: Code 1.50.1 (d2e414d9e4239a252d1ab117bd7067f125afd80a, 2020-10-13T15:06:15.712Z) OS version: Windows_NT x64 10.0.18363

System Info

Item	Value
CPUs	Intel® Core™ i5-6300U CPU @ 2.40GHz (4 x 2496)
GPU Status	2d_canvas: enabled flash_3d: enabled flash_stage3d: enabled flash_stage3d_baseline: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on oop_rasterization: disabled_off opengl: enabled_on protected_video_decode: unavailable_off rasterization: enabled skia_renderer: disabled_off_ok video_decode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled
Load (avg)	undefined
Memory (System)	15.88GB (5.36GB free)
Process Argv	–crash-reporter-id f652528b-5678-4b12-9ca0-3de6b1e1135f
Screen Reader	no
VM	0%

[steventartakovsky-vungle]

Also @DavidKutu, FYI it seems that the url of the remote connection gets cached and cannot be easily modified even after reload.

[clayms]

@DavidKutu sure, give me a few more days.