VS Code Integration Polishing

First of all, I think this extension is nothing short of incredible, both in the value it provides and in the technical problems it solved very well! Thanks so much for implementing it!

This extension is a real game changer for frontend development in codespaces, as without this extension it is very difficult to debug frontend code in a codespace.
It also solves the biggest problem I have with chrome dev tools, which is that jumping to source in the dev tools doesn't reveal the source in VS Code.

I do think however that there are a couple of (easy to implement) things that could significantly improve the integration into VS Code.

I created a bunch of issues for some things I noticed:

• https://github.com/microsoft/vscode-edge-devtools/issues/1886
• https://github.com/microsoft/vscode-edge-devtools/issues/1887
• https://github.com/microsoft/vscode-edge-devtools/issues/1888
• https://github.com/microsoft/vscode-edge-devtools/issues/1889
• https://github.com/microsoft/vscode-edge-devtools/issues/1890
• https://github.com/microsoft/vscode-edge-devtools/issues/1891
• https://github.com/microsoft/vscode-edge-devtools/issues/1892
• https://github.com/microsoft/vscode-edge-devtools/issues/1893

I hope I didn't spam you with these issues.
The extension is great already, but I think with a little bit of polishing, it could be even more amazing.

Start by reviewing the linked issues 1886 through 1893, since this issue only groups several VS Code integration concerns and names no files, tests, or entry points. Work is not defined as done until a specific concern and acceptance criteria are selected from those linked issues.