Switch to built-in "Simple browser"

[septatrix]

Clear and concise description of the problem

Currently there is a plethora of bugs with the embedded browser. It...

• requires a separate Chrome install (No Chrome installation found vscode-browse-lite#33),
  • also sometimes does not find the Chrome install,
  • thus has problems when running inside a sandbox like Flatpak or Snap,
  • thus does not work with VSCode Server (https://vscode.dev/),
• does not work with remote ssh/containers etc. (Work on Remote-SSH and Remote-Container vscode-browse-lite#32),
• is blurry on 4k monitors (4K display blurry #23),
• does not show <select> dropdown (Embedded browser <select> doesn't dropdown #24),
  • the same likely applies for other browser UI like datetime, color or file inputs,
• does not support uploads (Videos and uploads are not supported vscode-browse-lite#14),
• has problems with copy-paste (Is it possible to support copy text to other window vscode-browse-lite#29, Clipboard issues when copy / pasting vscode-browse-lite#5),
• does not support vscode:// URIs (Unable to access vscode: URIs in <a> elements vscode-browse-lite#19),
• has broken keyboard inputs (Embed Browser Enter-Key behavior bug vscode-browse-lite#2),
• the screensharing technique is very resource intensive
  • selecting text e.g. is laggy
  • CPU usage is high

Suggested solution

VSCode has a built-in "Simple browser" extension since a while ago: microsoft/vscode#109276

As it is a proper built-in extension and uses the rendering engine already embedded inside electron it does not suffer from the problems of the current screensharing architecture. This will likely resolve every issue listed above!

Alternative

Fix vscode-browse-lite, though I do not consider this worth the effort given the limitations of it architecture.

Additional context

The only drawback will be that devtools will be a bit less nice. One has to use the electron devtools (Help > Toggle Developer Tools) which are not in a nice tab like the current ones. However, I definitely consider this drawback justified given the amount of advantages this switch would bring.
Furthermore, one can still open it in an external browser if some parts of the devtools are limiting inside VSCode.

Validations

• Follow our Code of Conduct
• Read the Contributing Guide.
• Check that there isn't already an issue that request the same feature to avoid creating a duplicate.