Investigate possibility of not patching workspace language runtime images when running OpenShift v4

[ibuziuk]

For Che 7 GA release we did patching of language runtime images to make them compatible with OpenShift - https://github.com/eclipse/che-devfile-registry/tree/master/arbitrary-users-patch

The arbitrary-users-patch was done as part of the #13454

Basically, for OpenShift v3 it looks like there is no other possibility other than patching which is described in the official documentation - https://docs.okd.io/3.11/creating_images/guidelines.html#openshift-specific-guidelines

However, it looks like the situation changed dramatically in OpenShift v4 - openshift/origin#23369

CRI-O is the default contianer engine in OpenShift v4 which has the support of adding the entry of the user to the /etc/password if it does not exists in /etc/passwd.

We need to investigate the possibility of not patching any language runtime images and use them as-is on OpenShift v4.

Describe the solution you'd like

Need to investigate the possibility of not patching any language runtime images and use them as-is on OpenShift v4

Describe alternatives you've considered

Alternatively, we would need to continue patching images as done for OpenShift v3 - https://github.com/eclipse/che-devfile-registry/tree/master/arbitrary-users-patch

The verification of the arbitrary-users-patch compatibility with OpenShift v4 was done in #13960

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