Rework the "che-plugin-registry" image build using multistage dockerfile

[Ohrimenko1988]

Is your task related to a problem? Please describe.

Currently, building of the "che-plugin-registry" requires preinstalled tools on the local machine:

• nodejs
• yarn
• git

In my opinion it would be great to rework the current flow for using multi-stage docker flow.
It gives us several advantages:

• We will get rid of pre-build steps, all necessary tools will be already in the container
• Reduce the possibility of local environment issues
• Keep the image small

Describe the solution you'd like

Describe alternatives you've considered

Additional context

[benoitf]

it should not be a 'pure multi-stage' Dockerfile, but also publish both 'dev image' and a 'build image'
dev image allows 'dogfooding usage'

[benoitf]

BTW we already have the dev-image

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

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

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