Enhancement: Update Monaco to a newer version (>= 0.20.0)

[geckogreen]

Currently, OSD is using the monaco editor component in version 0.17.0.
This version is pretty old and we encountered some bugs, in particular

• horitontal scrolling with mousewheel does not work in Firefox
• copying selected text into the clipboard with Ctrl+C not working reliably

With version 0.20 the API editor.getContentHeight() was added which helps a lot to correctly size the editor if you
use line-wrap.

I would like to propose to update monaco-editor to at least version 0.20.0.
The above mentioned issues seem to be fixed with an upgrade to that version.

Are there already any plans to do this?
If not I could try to provide a pull request.

[joshuarrrr]

@geckogreen I don't think there are any imminent plans to upgrade it, but a PR would be welcome. Note that monaco-editor and react-monaco-editor are both wrapped by the Code Editor Component. The sizing functionality, in particular, sounds like you might need to refactor the resize detector in the current component.

As part of the PR, you'd need to provide some research and potentially mitigations for the breaking changes between 0.17.0 and 0.20.0:

0.19.0:

• getConfiguration() is replaced by getRawOptions(), which returns the passed in editor options.
• Starting with this version, the Monaco Editor no longer supports IE 11. The last version that was tested in IE 11 is 0.18.1.

0.20.0:

• Renamed onCompositionStart, onCompositionEnd to onDidCompositionStart, onDidCompositionEnd
• Changed the argument passed in to onDidPaste
• WorkspaceEdit.edits has now changed its shape such that edits must no longer be grouped by resource.
• The Monaco Editor no longer supports IE 11. The last version that was tested in IE 11 is 0.18.1.

Note that any version bump above 0.18.1 will likely be a breaking change for plugins depending on monaco-editor directly, so we wouldn't be able to backport (to 2.x or 1.x branches) as-is.

[joshuarrrr]

Assuming some of the above changes are breaking, we'd want to do 2 separate PRs for main and 2.x (with an alias), something along the lines of

• [Chore] Add vega-lite v5 dependency and bundle from source #3076
• [2.x] Add aliased vega-lite v5 dependency and bundle from source #3151

[SuZhou-Joe]

Assuming some of the above changes are breaking, we'd want to do 2 separate PRs for main and 2.x (with an alias), something along the lines of

• [Chore] Add vega-lite v5 dependency and bundle from source #3076
• [2.x] Add aliased vega-lite v5 dependency and bundle from source #3151

alias way has issues because the implementation of monaco-editor has side effects. Please check the Unit test error here.
#3438 .

[AMoo-Miki]

alias way has issues because the implementation of monaco-editor has side effects. Please check the Unit test error here. #3438 .

I think that aliasing is not done right.

[joshuarrrr]

This is no longer a blocker for the ISM team. It's still something we want to do, but not currently prioritized.