Pre package extensions and install them on startup for users

[melissa-barca]

Addresses #6302, #6301, #6305, #5315

Introduces the concept of "bootstrapped extensions". Bundles the following extensions as VSIX files with Positron:

• Black
• Posit Publisher
• Shiny(Workbench only)
• Quarto
• ms-toolsai.jupyter-keymap
• ms-toolsai.vscode-jupyter-cell-tags
• ms-toolsai.vscode-jupyter-slideshow
• ms-toolsai.jupyter
• ms-pyright.pyright
• ms-python.debugpy

When a user starts up Positron after first installing it or a version change (upgrade or downgrade), Positron will install the bootstrapped extensions for the users. Users will then be able to manage the extensions (upgrade, downgrade, uninstall, disable) themselves. Positron will always prefer whichever version of the extension in newer (bundled or user). When a user downgrades the extension, Positron will attempt to upgrade to the latest packaged version on the next upgrade, but not next Positron launch.

I changed the approach slightly from my initial spec. The initial spec built on top of the existing defaultExtensionInitializer. This approach is heavily inspired by that class but provides the server and desktop logic in src/vs/platform/extensionManagement/node/positronBootstrapExtensionsInitializer.ts.

Release Notes

New Features

• Packages several extensions that were previously shipped a built-in extensions as user managed extensions that are installed on first launch.

Bug Fixes

• N/A

QA Notes

@:web

[github-actions]

E2E Tests 🚀
This PR will run tests tagged with: @:critical @:web

^{readme  valid tags}

[jonvanausdeln]

The matplot lib test is failing due to missing positron-ipywidgets .. could that be something missed ?

[jonvanausdeln]

@melissa-barca I updated so the web based tests will run on the PR as well

[timtmok]

LGTM

[juliasilge]

I made a release build and a dev build and the extension experience is looking great!

For the failing test, I suspect what is happening is that our positron-ipywidgets extension, which is truly builtin, must somehow need one of the jupyter extensions to work and something is going wrong there. Here is our builtin extension:

https://github.com/posit-dev/positron/tree/main/extensions/positron-ipywidgets

@seeM I know you worked on this; do you have any thoughts on how our extension here uses other extensions, that we're trying not have builtin? I see there are no official dependencies for it.

[melissa-barca]

Thanks @juliasilge! I suspected something like that with the test, because it started failing when I moved the Jupyter tests over but like you mentioned, I didn't see a declared dependency. I'm wondering if I should move them (or isolate the problematic one and just move that one) back to built-in and file a separate issue for that.

[juliasilge]

If it is the main Jupyter extension, I would say that is one of the driving examples of us wanting this bundling type of experience; it would be great to resolve the failing test without moving it back to builtin.

[melissa-barca]

@juliasilge I did some local testing and the tests pass when I move jupyter-renderers back to built-in. How do you feel about keeping that one?

[juliasilge]

In the immediate short term, let's go for it! 🚀

For the slightly longer term, can you open an issue outlining why we couldn't bootstrap this one and move it to triage? We'll get it prioritized for a quick followup, to find out how to address the problem.

[melissa-barca]

Follow up issue for the Jupyter Notebook Renderers extension is here: #6507