We need a clean customer-friendly solution for deploying CRW 2 outside the operatorhub online context.

For 1.2, this was deploy.sh. For 2.0, this will rely on chectl, but with some constraints & different defaults. See also https://github.com/eclipse/che/issues/14489

Best case, the defaults for CRW 2 deployment will be encoded in upstream, like we do for che-operator's cheFlavor = "codeready".

Worst case, we'll need a new crwctl.sh script to wrap chectl and a customresource.yaml file to set the correct CRW defaults.