Fixes #46217

Fixes #44597

Fixes #45784

Changes the release notes to use the standard webview editor instead of their custom webview editor.

Also makes the release notes editor a singleton. Only one release notes editor may be open at a time.

Fixes #27493
Fixes #34369

Fixes #44039

Add a new option that lets extensions override which root folders a webview can load local resources from. Defaults to allowing any resource in the workspace

* Webview api

* Cleaning up markdown webview

* Hooking up dispose

* Fix some merge errors

* Use custom context key to show markdown title bar contributions

* Add basic on focus and on blur events

* Fixing find widget in webview

* Hookup _isDisposed

* Use new extension resource scheme to load markdown extension resources

* Documenting keep alive

Fixes #41887

Fixes #41795

Make sure we use the correct path seps and normalization on windows for the new webview protocol

* Allow loading webview outside of file: origin

**Problem**
Webviews are currently always loaded from a file on the disk. This results in the webview running in the file origin, potentially allowing it to access any file on disk. If a webview fails to sanitize workspace or remote input, untrusted code could potentially access files on the user's system.

**Fix**
Add a new option to serve the webview out of a "data:" uri instead. This prevents access to `file://` resources.

In order to allow webviews to still load resources from disk, add a new protocol called `vscode-core-resource://` that only allows access to resources inside of the vscode directory.

Moves extension pages and our release notes to use this new option. These already are pretty locked down. We cannot move the htmlpreview command to use this option as it would break a huge number of existing extensions, however the new webview API will always have this new option enabled.

* Shorted protocol name

Revert "Use simpleFind.xyz for simpleFind command IDS"

This reverts commit 9066eedc.

Revert "Review cleanup"

This reverts commit c0a21800.

Revert "SimpleFindWidget Re-Factor next,previous,history, single global commands Cleanup1"

This reverts commit 1a26638f.

Revert "Working SimpleFind Service, isolation - pre- cleanup"

This reverts commit bd8f5ebb.

Revert "Reveal Find on find n/p, add delayed update history"

This reverts commit c586e523.

Revert "Hide input focus tracker, cleanup"

This reverts commit 27f45235.

Revert "simpleFind Add next,previous,history fix"

This reverts commit b69d45bb.

* Refactored terminalFindWidget into a SimpleFindWidget and used that to provide find for webviews

* Refactored Webvieweditor into an abstract base and a concrete class to respect 'part' separation

* Cleaned up css and images that I forgot to delete

* Reset i18n.js file

* bind this when passing onThemeChange to themeService.onThemeChange

* Add 'CloseWebViewEditorFind' command to close find when pressing escape

* Ctrl+f now selects text in all SimpleFindWidgets even when buttons are focused. Aligns with full find widget

* Fixed issues when reactivating find

* Register webviewEditor with workbench

* Remove find widget when disposing webview

* Fixed webviewEditor casing in releaseNotesEditor (windows is case insensitive). Removed registration from workbench to see if it was necessary at all. If it fails again, I'll add it back

* Preserve Webview Scroll Position

Fixes #22995

**Bug**
If you switch away from an editor that users a webview, the scroll position is currently not preserved. This effects our release notes and the markdown preview. The root cause is that the webview is disposed of when the view is hidden.

**Fix**
Add some presisted state to track scrollProgress through the webview. Use this state in the standard html editor and in the release notes.

* Use view state

* Continue prototype memento based approach

* Preserve Webview Scroll Position

Fixes #22995

**Bug**
If you switch away from an editor that users a webview, the scroll position is currently not preserved. This effects our release notes and the markdown preview. The root cause is that the webview is disposed of when the view is hidden.

**Fix**
Add some presisted state to track scrollProgress through the webview. Use this state in the standard html editor and in the release notes.

* Revert changes to ReleaseNotesInput