Create jenkins job to build CRW containers outside Brew (with sed transforms) and push to Quay directly

Create jenkins job to build CRW outside Brew (in order to apply sed transforms) and push to Quay directly.

Purpose:

to have operator/metadata/repository images that refer to containers in Quay, rather than RHCC.

Benefits:

• This would facilitate testing as we'd no longer have to override registries with `oc apply`, or
• use custom resources to override image defaults in operator when deploying, and
• using crwctl would only require passing in the quay version of the operator rather than hardcoded reg.rh.io future 2.1 version., eg.
  • crwctl --che-operator-image=quay.io/crw/operator-rhel8:2.1
    • (assuming --tls, --self-signed-cert and --os-oauth are the new enabled defaults)

Old workflow:

• Jenkins sync job -> push commit from upstream GH to pkgs.devel repo -> update dependencies / tarballs -> trigger Jenkins job to drive Brew build
  • -> trigger Jenkins job to push to quay

New workflow:

• Jenkins sync job -> push commit from upstream GH to pkgs.devel repo -> update dependencies / tarballs -> trigger Jenkins job to drive Brew build
  • (DO NOT PUSH Brew build to quay) -> apply quay-related sed transforms -> build container in Jenkins -> trigger Jenkins job to push to quay

Affected images:

• operator
• operator-metadata
• devfileregistry
• pluginregistry

sed transforms:

s#registry.redhat.io/codeready-workspaces#quay.io/crw#g
(more?)

Future enhancement:

Support ability to also transform using @digest instead of :tag. (CRW-563)