add remote repo config

[ChristopherHX]

The azure-pipelines.repositories settings maps the external Repositories to local or remote folders.

Syntax [<owner>/]<repo>@<ref>=<uri> per line. <uri> can be formed like file:///<folder> (raw file paths are not supported (yet?)), vscode-vfs://github/<owner>/<repository> and vscode-vfs://azurerepos/<owner>/<project>/<repository>

[bryanbcook]

Glad to see you're adding the repositories and configuration settings.

I've pulled down the code and played with this a bit, though I'm having difficulty getting break-points to be hit.

[ChristopherHX]

I'm having difficulty getting break-points to be hit.

I didn't get source maps working, the dotnet js sources are already minified and don't play nicely with webpack.

I never tried Debugging .net in the webbrowser, but debugging js code works if you disable all breakpoints and reenable them after the extension is loaded and you set them in the dist/main.js file not the source code file.

I usually can debug the exension easier in a vscode in the webbrowser.
https://code.visualstudio.com/api/extension-guides/web-extensions#test-your-web-extension-in-a-browser-using-vscodetestweb
Somehow does the non web extension host test vscode instance hang for me and is super slow, but the vscode web version is super fast while testing and breakpoints are working without disabling and reenabling.

I had messed around webpack to pack the dotnet js files into a single file js files, because vscode webextension cannot use importScripts.

Adding a nodejs entrypoint using multiple files could make debugging easier