Tracking PR for monaco

[joneugster]

This PR keeps track of all modifications we'd like for using the vscode-lean4 with a monaco editor.

• depends on: feat: [lean4web] add option to change selectionMoveMove leanprover/vscode-lean4#508
• depends on: feat: [lean4web] customizable project precondition checks leanprover/vscode-lean4#497
• depends on: feat: [lean4web] abstract lean client setup for websocket clients leanprover/vscode-lean4#568
• depends on: feat: [lean4web] abstract the implementation of infoview as a webview leanprover/vscode-lean4#567
• depends on: feat: [lean4web] export RpcSessionAtPos leanprover/vscode-lean4#586

merged:

• depends on: refactor: replace require-style imports leanprover/vscode-lean4#504
• depends on: refactor: rewrite logger to be compatible with browser leanprover/vscode-lean4#494
• depends on: fix: dispose webviewPanel in InfoProvider.dispose leanprover/vscode-lean4#514
• depends on: fix: register event listeners for proper disposal of client provider leanprover/vscode-lean4#498

Further, there is one small fix to deal with mismatching client/server OS, but I'm not sure this would be the right fix in the extension. Therefore it's merely here for reference:

• depends on: fix: [lean4web] standardise URI for missmatching client/server OS #3
• depends on: fix: [lean4web] wait for changes to take effect before replacing abbreviations #4

Updating everything

Here are the steps to keep these PRs and the entire project up-to-date with vscode-lean4:master. Ideally these are done from within the submodule lean4monaco/src/vscode-lean4:

1. Synch master branch with upstream (can be done here with the github UI)
2. Reset your local master to a "Release" commit! This ensures no version clash with the published packages @leanprover/infoview etc.
3. On each PR linked here, rebase it to master and force-push.
4. Then update monaco branch. For example, reset it to master, then merge all branches listed here again (e.g. in the order provided).
5. now you can build lean4monaco
6. you might want to update for example npm update @leanprover/infoview in lean4monaco, too.
7. if the tests work, you can publish lean4monaco to npm, and then call npm update lean4monaco in lean4web.