Move stow / kubedoc and other internal features to the Universal Base Image

[ibuziuk]

Is your task related to a problem? Please describe

Move all internal Eclipse-specific configuration to the Universal Base Image:

• stow
• kubedoc
• smth. else?

In the context of the current issue, this should be done for ubi8 only

Describe the solution you'd like

(quay.io/devfile/base-developer-image:ubi8-latest the image should contain all Eclipse Che specific configuration

Describe alternatives you've considered

N/A

Additional context

Motivation https://issues.redhat.com/browse/CRW-6577

[dkwon17]

PR: devfile/developer-images#179

[ssbarnea]

@dkwon17 @ibuziuk Maybe one of you can give me a hint regarding where I can raise bug report about the https://github.com/devfile/developer-images repository as it seems to have the issue tracker disabled and the README.md file does not mention any alternative way to raise issues.

I noted:

• lack of arm64 image for universal (yeah, not so universal...)
• too many layers in universal, this has real performance issues and storage especially on some storage systems where it can have huge impact (like taking >40 disk space even if the image is much smaller). This can be addressed in two ways, either a better build logic that reduces the layers or using a layer squashing tool like docker-squash tool.

[ssbarnea]

Apparently we can use the smaller image to build a devspaces container, my PR that makes the switch is at ansible/ansible-dev-tools#393 but I still need to perform some tests with it, just to be sure.

[ibuziuk]

@ssbarnea hello, you can raise upstream issues in https://github.com/eclipse-che/che/issues
The current plan is to deprecate and remove ubi 8 from the upstream UDI codebase (ubi 9 should be only supported version in the upstream) as part of #23034
N.B. arm64 is planned to be added for UBI 9 as part of this issue