Plugin model for next gen Che

[ashumilova]

We need to define the plugin model for next gen Che:

• Client side only plugin
• Server side only plugin
• Client and Server side plugin
• Client and Server as sidecar plugin
  A plugin will be be packaged in a way to allow those different cases.

The more details are described in the document

And here is the list of tasks that should be investigated and implemented to archive the new plugin model:

• Implement the proxy for plugins API Implement the proxy for plugins API #9063
• Investigate the better way for providing list of plugins to web worker Investigate the better way for providing list of plugins to web worker #9068
• Create Theia plugin that introduces new extension model Create Theia plugin that introduces new extension model #9064
• POC of server communication with the server plugin and browser POC of server communication with the server plugin and browser #9183
• Add support for plugins registry Add support for plugins registry #9208
• Define plugin's metadata and it's storage Define plugin's metadata and it's storage #9210
• Refresh frontend/backend plugin parts on plugin disabled state Refresh frontend/backend plugin parts on plugin disabled state #9211
• Plugin API definition and impelementation Plugin API definition and implementation #9215

[skabashnyuk]

Please note, to avoid problems with CORS, authentication and port range. It would be great to organize client plugins so they communicate server with a single port.

[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.