Uplift Monaco to VSCode v. 1.65.2

[colin-grant-work]

What it does

Fixes #10387.

This PR has two main objectives:

• Update our code to use Monaco@32.1(+)

The (+) indicates that the actual code at @theia/monaco-editor-core@0.32.1-alpha0 is ahead of the Monaco release 0.32.1. The current plan is to wait for the next VSCode release, then peg our code to that, and perhaps label @theia/monaco-editor-core with the VSCode version number rather than the monaco-editor-core version number.

• Update our code to use Webpackable modules, rather than Asynch Module code with custom loaders. This allows us to be transparent about what Monaco code is being consumed where in our code base, and makes it easier to know where we're using public API (import * as Monaco from '@theia/monaco-editor-core') vs. private API (import { whatever } from '@theia/monaco-editor-core/*')

In addition, it includes the TypeScript source in the @theia/monaco-editor-core NPM package, so it is possible to simply click through to definitions in the source, making it easy to explore the Monaco code running in Theia.

This PR does not (for the most part):

• change the way we're using Monaco, clean up (much) Monaco-related code, or implement new features with the Monaco functionality. There is plenty of scope for this work, but it seems best to separate the uplift itself from new feature development.

I've added a file called uplift-journal.md in packages/monaco - have a look there for some observations about the process. I will be migrating that content to documentation in the wiki over the next little while.

How to test

Testing instructions can be found here.

Review checklist

• As an author, I have thoroughly tested my changes and carefully followed the review guidelines

Reminder for reviewers

• As a reviewer, I agree to behave in accordance with the review guidelines

[colin-grant-work]

@msujew, this is still a ways off from being ready, but one problem that's arisen is that even strings copied from Monaco at a newer version aren't present in our current nls.metadata.json. Do you have any thoughts about how we want to maintain that file and handle changes in our Monaco and VSCode API targets / dependencies?

[colin-grant-work]

@planger, the one CI check failing here is Playwright, and as we've discussed, it's the change to the default value of editor.autoSave in the browser that's throwing the test off by saving the editor when it's expected to be dirty. How would you like to address that change?

[planger]

@colin-grant-work I would suggest to extend the TheiaEditor in order to allow setting the editor.autoSave preference via the main menu and then toggle it off before the test in beforeAll.

But, please feel free to just skip the test in this PR, so your PR is green, and I'll open an issue that we'll resolve soon. WDYT?

[colin-grant-work]

@planger, thanks for the input. I have disabled the test for now, and it looks like @ndoschek has already created the corresponding issue so thanks to her, as well.

[msujew]

I'll add my approvement as well, since I already gave it unofficially at the dev-meeting. The change is looking good to me, thanks Colin!