Create 'master', 'nightly', 'release' CI for 'che-machine-exec' plugin and move images to quay.io

Is your task related to a problem? Please describe.

Create ‘master’, ‘nightly’, ‘release’ CI for ‘che-machine-exec’ plugin and move images to quay.io. This is already done for plugin and devfile registries - https://quay.io/organization/eclipse

Currently, for machine-exec there is only codenvy ‘release’ CI that should be decommissioned - https://ci.codenvycorp.com/view/release/job/release-che-machine-exec-plugin/

[ibuziuk]

@vparfonov @l0rd I would propose to use quay.io for 7.2.0 release and deprecate the docker one for che-machine-exec

[ibuziuk]

I would propose the following CI / tags:

• master - CI is triggered on master commits and tags based on the git commit hash & pushes to quay.io
• nightly - CI is triggered from the master branch on a daily basis and pushes nightly images to quay.io
• release - CI is triggered from the release branch, tags images based on the VERSION file e.g 7.2.0 and pushes images to quay.io

@vparfonov @AndrienkoAleksandr I do not think other tags are needed like e.g. next 7.0.0-next that present in https://hub.docker.com/r/eclipse/che-machine-exec/tags If those are needed please clarify the use-case.