Develop discovery mechanism for launching remote plugins

[vitaliy-guliy]

Description

As a developer of a remote plugin I would test it in my workspace which have dedicated containers for launching the remote plugin and for Theia.

To launch remote plugin (aka endpoint) I have to:

• have cloned and built theia-endpoint-runtime Theia extension
• open terminal for launching remote plugin
• go to theia/che/che-theia/dockerfiles/theia-endpoint-runtime directory
• set THEIA_PLUGINS and THEIA_PLUGIN_ENDPOINT_PORT environment variables
• launch plugin-remote.js with node

To launch Theia i have to

• have cloned and built Theia
• open terminal for launching Theia
• go to theia/examples/assembly directory
• get generated URI for the remote plugin from the workspace runtime
• set THEIA_PLUGIN_REMOTE_ENDPOINT_..... environment variable and specify ID of the endpoint and plugin URI
• run Theia

It's very inconvenient to do all of this by hands.
I would prefer to have a mechanism for running that by a command.

[vitaliy-guliy]

Sample plugin simplifies launching and developing of remote plugins https://github.com/eclipse/che-theia/issues/96

[garagatyi]

Seems relevant #12395 (comment)

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

[vitaliy-guliy]

It's not actual anymore.