MON-3792: fix metrics-server path for /test versions

[rexagod]

Owing to the older path being referenced in the prow workflow, we saw consistent failure for /test versions job, this fixes that.

---

• [ ] I added CHANGELOG entry for this change.
• [x] No user facing changes, so no entry in CHANGELOG was needed.

[machine424]

Thanks /lgtm

[openshift-ci[bot]]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: machine424, 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: - ~~[OWNERS](https://github.com/openshift/cluster-monitoring-operator/blob/master/OWNERS)~~ [machine424,rexagod] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment

[machine424]

/hold cancel

[openshift-ci-robot]

@rexagod: This pull request references MON-3792 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.16.0" version, but no target version was set.

In response to [this](https://github.com/openshift/cluster-monitoring-operator/pull/2286): >Owing to the older path being referenced in the prow workflow, we saw consistent failure for /test versions job, this fixes that. > >*** > >* [ ] I added CHANGELOG entry for this change. >* [x] No user facing changes, so no entry in CHANGELOG was needed. > Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fcluster-monitoring-operator). 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]

/jira refresh /test e2e-aws-ovn-single-node

[openshift-ci-robot]

@rexagod: This pull request references MON-3792 which is a valid jira issue.

In response to [this](https://github.com/openshift/cluster-monitoring-operator/pull/2286#issuecomment-2037314343): >/jira refresh >/test e2e-aws-ovn-single-node Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Fcluster-monitoring-operator). 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-agnostic-operator

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 953011b1a4cdd66e2b42e16facca4ccc65079b7e and 2 for PR HEAD 46b4bba5680b992ba7aefee0b74fb43f0818b326 in total

[openshift-ci[bot]]

@rexagod: all tests passed!

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/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).

[openshift-bot]

[ART PR BUILD NOTIFIER]

This PR has been included in build cluster-monitoring-operator-container-v4.16.0-202404050447.p0.g5520bbc.assembly.stream.el9 for distgit cluster-monitoring-operator. All builds following this will include this PR.