Consume ESM build of VS Code

[tsmaeder]

Feature Description:

VS code is moving to use ESM as their internal module system (microsoft/vscode#226260). While they might produce ALM builds for a while longer, we need to get ready to consume the ESM version of VS Code.
Our target module systems are webpack and nodejs. Both of those are able to load ESM modules from CommonJS modules. So we should be able to continue shipping Theia as a CommonJS framework. Moving Theia to ESM would affect all adopters, since importing CommonJS modules (Theia extensions) from the Theia framework is unlikely to work. Adopters would be forced to move to ESM, as well.

[tsmaeder]

I was able to build the ESM version of @theia/monaco-editor-core of VS Code 1.93.1, but webpacking fails because of the dynamic ESM import in editorSimpleWorker.js 424:16-32. The system then tries to load all *.d.ts files in that directory and croaks. There is a ContextReplacentPlugin in webpack that should allow to fix this, but so far, no dice.

[tsmaeder]

I've been able to resolve the webpack issues by writing a webpack plugin, but with 1.93.1, there are now problems with the monaco-services we override/implement (circulare DI dependencies).

[tsmaeder]

Superseded by #14726