We are testing crwctl tarball from "quay" channel on https://codeready-workspaces-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/CRW_CI/view/Pipelines_Next/job/crwctl_2.4/, because don't have images on registry.redhat.io during pre-release testing, and can't mirror registry.redhat.io to registry.stage.redhat.io on QE OCP 3.11 https://issues.redhat.com/browse/CRW-1205

At the same time "redhat" channel is aimed to build crwctl tarball for production.

crwctl tarball from "quay" channel has pointed to latest images on quay.io, so it brings a risk not to catch issues with default installation, like https://issues.redhat.com/browse/CRW-1273.
So, we need to test crwctl tarball from "redhat" channel as well to mitigate the risk.