Support private extension packs and private extension dependencies

[lachaib]

Fixes #30

I had to shake some rust off my VS Code extension development, but it seems to be doing the job, I'd be glad to get someone to test it

[colas31]

Hello @lachaib ;) Hope you are good.

I can run some tests if needed. Tell me what I should do to test this PR properly.

[lachaib]

Hi @colas31 , To test this, you may pull the branch, build the extension and install extension from the built vsix.

• I'm assuming you have private registries already available, the first thing that would come to my mind would be to assert there is no regression, i.e. you are able to install or update an extension as you did before.
• Secondly, it would be nice to create an extension pack with one or more of the private extensions you have in your registry, publish it to your private registry and try to install it (with the private extensions it should pull not already installed), and check that install works just fine.
• And last, there was also an opportunity to use private registries as cache for extensions from marketplace (for people behind strict firewalls), so you may pull some extensions and extension packs (e.g. python) from marketplace to the private registry and see that when installing them from the private registry the pack and all its dependencies are pulled together from the registry.

That's what I'd do if I was still in my previous company and had a private extension registry. Thanks for your help

[kumar121193]

@lachaib @colas31 Any update on this?

[lachaib]

Not on my side, I'm still waiting feedback from someone eager to test, if you want to test it yourself I explained the procedure.

[colas31]

Unfortunately I didn't get time to test. And I just changed my position job. It will be more difficult for me to perform the test.

[kuenzign]

Has there been any update on this? Having private extension packs would be very beneficial.