Some of the largest demand for WMCO comes from bare metal (BM) deployments. In order to officially support BM we need to be actively testing WMCO on bare metal in CI. This ticket covers changes to the openshift/release repo to get a job available for us to run on WMCO PRs.

Engineering Details:
After talking with the metal team about this, I opened up a PR with a proper devscripts setup, thinking our tests would at least be able to deploy the operator. Unfortunately the test pod was unable to create the WMCO namespace due to kubernetes permission issues:

```
INFO[2021-05-04T20:44:58Z] Logs for container test in pod baremetal-e2e-operator-windows-e2e-operator-test:
INFO[2021-05-04T20:44:58Z] hack/run-ci-e2e-test.sh -t basic
INFO[2021-05-04T20:44:58Z] Error from server (Forbidden): namespaces "openshift-windows-machine-config-operator" is forbidden: User "system:serviceaccount:ci-op-0pr4kzzn:baremetal-e2e-operator" cannot get resource "namespaces" in API group "" in the namespace "openshift-windows-machine-config-operator"
INFO[2021-05-04T20:44:58Z] Error from server (Forbidden): namespaces is forbidden: User "system:serviceaccount:ci-op-0pr4kzzn:baremetal-e2e-operator" cannot create resource "namespaces" in API group "" at the cluster scope
```

After talking with the metal team some more, it seems the reason is that "the cluster is deployed into a remote Packet instance, and usually steps that need to interact in some way with it need to ssh into the Packet instance, for example https://github.com/openshift/release/blob/3371478ffdcb41d51232e8ecbc3dccef0fc5ab99/ci-operator/step-registry/baremetalds/e2e/test/baremetalds-e2e-test-commands.sh#L86-L90"

Additionally there is a doc on metal CI https://docs.google.com/document/d/1LycdxwHpsWgKICRpt8eK77StThqi12oKs8aw202EI0w/edit?usp=sharing

Acceptance Criteria:

• WMCO CI contains a bare metal job which is able to deploy the operator without error. This job should have `always_run` set to false.