Expose DWO and DWCO images in CSV as RELATED_IMAGE_* env vars (like all the other images deployed by the Che Operator)

[tolusha]

Is your task related to a problem? Please describe.

DWO and DWCO images are defined in templates that are embedded into operator image.
It is not easy to replace them in downstream.

Current implementation also prevents using:

• digest pinning (instead of floating tags)
• offline deployments on OCP 4.x (cannot use built in OCP functionality with RELATED_IMAGE env vars)

Describe the solution you'd like

For productization purposes, and to be consistent with all the other images that the Che Operator deploys to a cluster, we need to add DWO and DWCO images to the deploy/operator.yaml and CSVs as RELATED_IMAGE_* env vars.

This will also empower use of DWO and DWCO images in arigapped deployments.

Care should be made to ensure that downstream sync scripts in crw-operator/build/scripts/sync-*.sh are also updated accordingly to point to the correct image names downstream.