For #96436

Caches the custom editors information using a global memento. This makes sure the editor information is available during startup before extensions have been initialized

* Add vscode-webview-resource protocol

Adds a new protocol (`vscode-webview-resource`) for loading resources insides of webviews. This replaces the existing `vscode-resource` protocol and is registered on the main thread instead of in each renderer

This change also adds some rewriting logic to update any `vscode-resource:` references found in the main html to use `vscode-webview-resource` instead.

* Move webview protcol provider to own file

* Remove registration of vscode-resource scheme

* Remove use or parition for each webview

Now that we have a single shared protocol handler, we do not need to run each webview in its own partition

* Fix rewriting csp to use new protocol

* Update src/vs/code/electron-main/app.ts
Co-authored-by: NBenjamin Pasero <benjpas@microsoft.com>
Co-authored-by: NBenjamin Pasero <benjpas@microsoft.com>

Fixes #97271

Fixes #96527

With the unified reopen-with code, we were no longer calling into the custom editor when reopening a custom editor with the default text editor. This change fixes that by making the custom editor explicitly provide the default editor as one of its overrides

Better fix for #96591 to also work correctly with notebooks

In the explorer->open with command, we need to call `getEditorOverrides` but do not have a real editor input. Rather than creating a fake editor input, we should just take uri for `getEditorOverrides`

Fixes #96591

Fixes #96484

The new toggle editor type command lets you quickly switch between a custom editor and our default editor

For #77131

This change primarly adds a new `Open with...` entry to the explorer context menu. To do this however, I had to make a few other changes:

- Add a new explorer context key for availible editors
- Moved the editor select prompt into a new function called `openEditorWith`
- Use `openEditorWith` for the new `open with` explorer command as well as for the `reopen with` command

For #94408

Moves this out of custom editors

This also adds a `availableEditors` context key that consists of a comma seperated list of editor ids that can be used for `reopen with`

#77131

For #94408

Fixes #93380

Allow closing a dirty custom editor even if the providing extension has been uninstalled

For #77131

Fixes #93963
Fixes #94515
Fixes #94517
Fixes #94527
Fixes #94509
Fixes #94514
Fixes #93996
Fixes #93913

This removes explicit edits from the API and reshapes the API to more closely match VS Code's internal API. The change also tries to better express the lifecycle of backups

Fixes #93857

For #94491

- Removes the mime field since it is not used
- Add default snippet
- Slightly improve wording

Fixes #94368

Fixes #94383

Fixes #93850

Make sure restored custom editors correctly track being dirty even if they have not been activated yet

Fixes #93863

This reverts commit c817576c.