Reworking external opener implementation to allow configured openers to be called directly without a canOpen check

If the user has configured a specific external uri opener, we should always try to use that without first calling `canOpen` to filter down the list of openers.

This change also adds `ExternalUriOpenerEnablement` which allows an opener to mark itself as the preferred opener for a given uri. If only a single preferred opener is returned, it will be used automatically for that uri (although user configuration can override this)

- Add error notification if opener throws an exception
- Add public facing id to openers. This is used in settings
- Add intellisense for the opener id setting

For #109277

- Add more explicit two phase structure to api
- Make opener pass along label when registered

This workbench service handles opening external uris. Unlike the core OpenerService, it also has logic for configuring a default opener and prompting if multiple openers are availble for a given uri

Part of #113827

This changes makes a few changes to the openers:

- Move the opener prompting from the extension host into the main thread
- Make the external opener process two phases: get openers and then open. This would let us skip the trusted domain validation for extension handled links if we want to in the future
- Add lifecycle to commands used by the uri opener

For #109277

This change moves the extension uri opener contribution point to instead use the internal `IExternalOpener` api instead of the more generic `IOpener` api. This is required since external uri openers should see the resolved uri that has gone through port forwarding, not the raw uri that the user clicked on

This change allows remote extension to handle elevation if they want.
Fixes microsoft/vscode-remote-release#3922

Fixes #112446: Avoid timeouts in mirroring terminals to the extension host by assigning a temporary UUID to terminals created on the extension host side

Fixes microsoft/vscode-internalbacklog#1680

And filter out the renderer.
Fixes #4185, #4110

Part of microsoft/vscode-remote-release#4112

show diaglog when extensions participate in file operations, have "don't show again" option and command to reset choice, add logging

For #109277

apply workspace edit from onWill-handler from within renderer, https://github.com/microsoft/vscode/issues/111878

* Allow status items with error background color (fix #110214)

* rename to statusBarItem.errorBackground

* address feedback and add error colors

* address feedback

Part of microsoft/vscode-remote-release#4021

Fixes #110795

Fixes #110795

* wip

* wip

* wip

* wip

* wip

* wip

Part of microsoft/vscode-remote-release#4021

* wip: try to use vscode.open and vscode.diff in git/scm

related to #110397

* 💄

* revert change to commands.converter.toInternal

* complete usage os vscode.open and vscode.diff in git extension