Better intellisense in the web version of jupyter extension

[rchiodo]

We have this situation here:

Pylance in the web is basically nerfed. This issue is to figure out a way to use the remote jupyter compute to generate better intellisense.

[rchiodo]

/cc @heejaechang @debonte @dbaeumer

[rchiodo]

Ideas for implementing:

Proxy idea

• Adding middleware to Python extension that drops all requests when in the web on a notebook (like we had before)
• Jupyter extension then install node and runs pylance on remote machine
• Jupyter extension proxies LSP requests through jupyter to this remote pylance

Web client idea

• Use languageclient web interface
• Start an LSP server on the remote jupyter box that serves up the web server?
• Not sure if this is a thing or not.

File API idea

• Add a file api to LSP where the server can ask the client for the contents of a file
• Jupyter tells python about the API and it's used by the web pylance to read files from the remote jupyter machine
• Would require implementing this first: Add service-worker based cancellation (and maybe RPC) for use in vscode.dev by synchronous LSs vscode#148967

[heejaechang]

let me tag Barry who is working on azure notebook for similar structure @barryt2