Add various mechanisms for preventing Eclipse Che breakages after updates in devfile GitHub org

[ibuziuk]

Is your task related to a problem? Please describe

Eclipse Che is a devfile-centric project. However, the contributions to devfile.io are not verified against Eclipse Che and we adapt reactively to the changes, and sometimes find the issues very late. Examples are in the Additional context.

Describe the solution you'd like

every contribution to devfile org should be verified against Eclipse Che https://github.com/devfile using various mechanisms - unit tests, github actions etc.
The goal is to find problems and incompatibilities in devfile repos pro-actively, not reactively

Describe alternatives you've considered

N/A

Additional context

Related issues that illustrate the current problems:

• nodejs 2.0 and 2.2 devfiles use terminating image under the hood and not usable by Eclipse Che devfile/api#767
• low memory limit for the quarkus devfiles which results in OOM during execution of the 'init-compile' command devfile/api#768
• fix: bump devfile/api dependency to resolve validation issue devfile/devworkspace-operator#821
• Many devfiles fail to validate under v0.14.0 devfile/devworkspace-operator#816

[l0rd]

Related (subtask of) devfile/api#681

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