Based on discussion at today's CRW cabal Mario would like to have a DWO operator in RHEC independent of CRW, but still releasing on a 6wk cadence. Goal is to start this for CRW 2.11 timeframe.

The reason for this is that both CRW and WTO depend on this shared image. RHEC can expose this (or we can hide it) but it's unclear if there's a customer need to deploy it by itself.

Note: this could be a good candidate for doing a small POC for CPAAS-993.

Requirements:

• create new product in Comet, Errata, etc.
• request new operator/metadata images in Comet, plus new pkgs.devel repos (unless we can skip this by using CPaaS?)
• release new operator, operator-metadata images under a new organization (devworkspace? devfile?)
• migrate crw/devworkspace-controller image to new org

• migrate Che operator to use this new image instead of the upstream Che version
• migrate CRW operator to use this new image instead of CRW version
• migrate WTO to use this new image instead of its internal one

It's been decided to make this simply an operatorhub "component" instead of a Product (as we did for WTO).

Likely won't require marketing or separate docs (just references to it via WTO and CRW install guides, as this DWO image would be part of the operator's payload and relevant to airgap deployments).