Rather than a separate job to maintain, we should make push-latest-containers-to-quay call push-container-to-quay several times for each container to be pushed.

That way we don't have similar logic in two places (dupe code == more maintenance) .

As part of this exercise we should convert both jobs to Jenkinsfile

• https://codeready-workspaces-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/CRW_CI/view/Releng/job/push-latest-containers-to-quay/configure
• https://codeready-workspaces-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/CRW_CI/view/Releng/job/push-container-to-quay/configure

This will also ensure that any special logic (like CRW-1011 for theia-rhel8 image) will be run any time we push to Quay.

DoD:

• new job + Jenkinsfile to replace https://codeready-workspaces-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/CRW_CI/view/Releng/job/push-latest-containers-to-quay
• new job + Jenkinsfile to replace https://codeready-workspaces-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/CRW_CI/view/Releng/job/push-container-to-quay
• rename old jobs to some backup name
• rename new jobs to use old names (so we don't have to update links and other jobs)
• verify both new jobs can push 1 image to quay, several images to quay, or all images to quay (except 2 registries + operator-metadata)
• verify digests for OSBS and Quay images are the same for the same tag (eg., 2.2-10, 2.2, and latest)