Che Plugins Dependencies Resolution

[l0rd]

Is your enhancement related to a problem

We allow vs code extensions to run in their own, remote from theia, container.
As a consequence vs code extensions aren't able to "see" extensions that are running in other containers. That has all sort of problems when 2 che plugins reference the same vs code extension (that get loaded twice) or when one vs code extension needs to call another extension at runtime (that get downloaded from the marketplace and in the wrong container...).

A comprehensive description of these problems is described in this google doc.

Discussion document:
https://docs.google.com/presentation/d/1T1v8jfHArOnT_KjFaKwSYYyPB7dhs6tjOoJtmDaRUVw/edit#slide=id.g6ea84496cc_0_224

Describe the solution you'd like

As a short term solution we envision to:

• disable automatic extension dependency resolution in che-theia
• warn users if an extension is downloaded twice Check plugins' extensions for conflicts during metadata broker che-plugin-broker#93

And the long term solution is about:

• rework theia endpoint to let extensions "see" remote extensions (list, get, call)
• support running in the same container plugins that reference the same image Run vsx in same container if the container specs match #15373
• support specifying che-plugins as dependencies of other che-plugins [meta.yaml / Che plug-ins]: Add dependencies section #15376
• re-enable automatic extensions dependency resolution but with the ability to specify an alternative marketplace

[che-bot]

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

[ericwill]

It would make plugin-registry automation a lot easier if we could remove the dependent vsix's from the meta.yaml files.