Add resource limits/requests to the devfiles and plugins in the registries

[l0rd]

Is your enhancement related to a problem? Please describe.

If no limits are set the Che default will be inferred. That may result in workspace not able to be scheduled in the Kubernetes cluster.

Describe the solution you'd like

Look for CPU/memory request and limits for each plugins and explicitely specify them. The same for containers components in devfiles.

Additional context

• Specify che-theia CPU limit (issue / PR)
• Specify jwt-proxy CPU limit (issue)
• Specify che-theia-plugins CPU limits (PR)
• Specify che-machine-exec and remote-runtime-injector CPU limits (PR)
• Specify che-theia-plugins memory requests in che-theia-plugin.yaml (PR)
• Add a che-plugin-registry PR check to avoid editros or plugins without mem/cpu requests and limits (PR)
• Evaluate target namespace ResourceQuota and LimitRange to evaluate and applyg the best mem/cpu requests and limits will be solved in the context of this epic

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