NO-JIRA: address `MetricsCollectionProfiles` failures on `metal` platform

[rexagod]

Address MetricsCollectionProfiles failures on metal platform due to the absence of a CMO configuration.

---

Branched off of https://github.com/openshift/origin/pull/29265 since we do not want to run these tests on all platforms yet (that'll happen once this makes it into the default set of features).

[openshift-ci-robot]

@rexagod: This pull request explicitly references no jira issue.

In response to [this](https://github.com/openshift/origin/pull/29284): >Address `MetricsCollectionProfiles` failures on `metal` platform due to the absence of a CMO configuration. > >*** > >Branched off of https://github.com/openshift/origin/pull/29265 since we do not want to run these tests on all platforms yet (that'll happen once this makes it into the default set of features). Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Forigin). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.

[rexagod]

/test e2e-gcp-ovn-techpreview

Mentioning here that I wasn't able to test this out since it's not possible to spin up a 4.18 metal cluster through cluster-bot currently, or do a /test e2e-metal-ipi-ovn-techpreview, so I believe the only way to run this on metal is to get this in.

[jan--f]

/lgtm

[openshift-ci[bot]]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jan--f, rexagod

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files: - ~~[test/extended/prometheus/OWNERS](https://github.com/openshift/origin/blob/master/test/extended/prometheus/OWNERS)~~ [jan--f,rexagod] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment

[rexagod]

/retest-required

[openshift-ci[bot]]

@rexagod: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-gcp-ovn-techpreview	67eb9a033436fa72bf315c53aa9970680d5b56ef	link	false	/test e2e-gcp-ovn-techpreview
ci/prow/e2e-aws-ovn-single-node	67eb9a033436fa72bf315c53aa9970680d5b56ef	link	false	/test e2e-aws-ovn-single-node
ci/prow/e2e-aws-ovn-kube-apiserver-rollout	67eb9a033436fa72bf315c53aa9970680d5b56ef	link	false	/test e2e-aws-ovn-kube-apiserver-rollout
ci/prow/e2e-openstack-ovn	67eb9a033436fa72bf315c53aa9970680d5b56ef	link	false	/test e2e-openstack-ovn
ci/prow/e2e-aws-ovn-single-node-serial	67eb9a033436fa72bf315c53aa9970680d5b56ef	link	false	/test e2e-aws-ovn-single-node-serial
ci/prow/e2e-aws-ovn-cgroupsv2	67eb9a033436fa72bf315c53aa9970680d5b56ef	link	false	/test e2e-aws-ovn-cgroupsv2
ci/prow/e2e-aws-ovn-single-node-upgrade	67eb9a033436fa72bf315c53aa9970680d5b56ef	link	false	/test e2e-aws-ovn-single-node-upgrade

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 5e5936850ca985288e8715b48c9f6e4e8b3b3687 and 2 for PR HEAD 67eb9a033436fa72bf315c53aa9970680d5b56ef in total