NO-ISSUE: Add Capability and FeatureGate checks to OLMv1 tests

[tmshort]

This required:

go get github.com/openshift/api@a2817b89f7e0989016967055a142d5e88bed18de
go get github.com/openshift/client-go@923091dd2b1a3d6fe75a06cc4f45972a3ddf84c2
go get github.com/openshift/library-go@0064ad7bd060b9fd52f7840972c1d3e72186d0f0
// update the replaces of k8s.io/kubernetes to github.com/openshift/kubernetes@v1.30.1-0.20241111135607a3f31a4f2c58 
go mod tidy
go mod vendor

/hold until capability is fully implemented

[openshift-ci[bot]]

Skipping CI for Draft Pull Request. If you want CI signal for your change, please convert it to an actual PR. You can still manually trigger a test run with /test all

[tmshort]

/test all

[openshift-ci[bot]]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: tmshort Once this PR has been reviewed and has the lgtm label, please assign bertinatto for approval. For more information see the Kubernetes Code Review Process.

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

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

[openshift-ci-robot]

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

In response to [this](https://github.com/openshift/origin/pull/29283): >This required: > >``` >go get github.com/openshift/api@a2817b89f7e0989016967055a142d5e88bed18de >go get github.com/openshift/client-go@923091dd2b1a3d6fe75a06cc4f45972a3ddf84c2 >go get github.com/openshift/library-go@0064ad7bd060b9fd52f7840972c1d3e72186d0f0 >// update the replaces of k8s.io/kubernetes to github.com/openshift/kubernetes@v1.30.1-0.20241111135607a3f31a4f2c58 >go mod tidy >go mod vendor >``` >/hold until capability is fully implemented 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.

[tmshort]

/retest

[tmshort]

/retest

[tmshort]

/retest

[tmshort]

/retest

[openshift-ci[bot]]

@tmshort: 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-metal-ipi-ovn-kube-apiserver-rollout	adac1cd337c9fbaef361be0975b8044b3f06dcd0	link	false	/test e2e-metal-ipi-ovn-kube-apiserver-rollout
ci/prow/e2e-gcp-ovn	adac1cd337c9fbaef361be0975b8044b3f06dcd0	link	true	/test e2e-gcp-ovn
ci/prow/e2e-metal-ipi-ovn-ipv6	adac1cd337c9fbaef361be0975b8044b3f06dcd0	link	true	/test e2e-metal-ipi-ovn-ipv6
ci/prow/e2e-aws-ovn-single-node-serial	adac1cd337c9fbaef361be0975b8044b3f06dcd0	link	false	/test e2e-aws-ovn-single-node-serial
ci/prow/e2e-aws-ovn-single-node-upgrade	adac1cd337c9fbaef361be0975b8044b3f06dcd0	link	false	/test e2e-aws-ovn-single-node-upgrade
ci/prow/e2e-metal-ipi-ovn	adac1cd337c9fbaef361be0975b8044b3f06dcd0	link	false	/test e2e-metal-ipi-ovn

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-trt-bot]

Job Failure Risk Analysis for sha: adac1cd337c9fbaef361be0975b8044b3f06dcd0

Job Name	Failure Risk
pull-ci-openshift-origin-master-e2e-metal-ipi-ovn-kube-apiserver-rollout	High [sig-network] can collect pod-to-pod poller pod logs This test has passed 100.00% of 11 runs on jobs ['periodic-ci-openshift-release-master-nightly-4.18-e2e-metal-ipi-ovn-kube-apiserver-rollout'] in the last 14 days. --- [sig-arch][Late][Jira:"kube-apiserver"] collect certificate data [Suite:openshift/conformance/parallel] This test has passed 100.00% of 11 runs on jobs ['periodic-ci-openshift-release-master-nightly-4.18-e2e-metal-ipi-ovn-kube-apiserver-rollout'] in the last 14 days. --- [sig-network] can collect host-to-pod poller pod logs This test has passed 100.00% of 11 runs on jobs ['periodic-ci-openshift-release-master-nightly-4.18-e2e-metal-ipi-ovn-kube-apiserver-rollout'] in the last 14 days. --- [Jira:"Network / ovn-kubernetes"] monitor test pod-network-avalibility setup This test has passed 100.00% of 11 runs on jobs ['periodic-ci-openshift-release-master-nightly-4.18-e2e-metal-ipi-ovn-kube-apiserver-rollout'] in the last 14 days. --- Showing 4 of 6 test results
pull-ci-openshift-origin-master-e2e-gcp-ovn	High [sig-network-edge][Conformance][Area:Networking][Feature:Router] The HAProxy router should pass the gRPC interoperability tests [apigroup:route.openshift.io][apigroup:operator.openshift.io] [Suite:openshift/conformance/parallel/minimal] This test has passed 100.00% of 33 runs on jobs ['periodic-ci-openshift-release-master-ci-4.18-e2e-gcp-ovn'] in the last 14 days.
pull-ci-openshift-origin-master-e2e-metal-ipi-ovn-ipv6	IncompleteTests Tests for this run (101) are below the historical average (2704): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)
pull-ci-openshift-origin-master-e2e-metal-ipi-ovn	IncompleteTests Tests for this run (101) are below the historical average (2514): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)

[tmshort]

Closing in favor of #29290