NO-JIRA: managed services: centralize definition of namespaces

[stbenjam]

Some ephemeral pods in rosa namespaces like openshift-sre-pruning are triggering failures that didn't have per-pod exceptions, just skip examining these namespaces alltogether.

Example: https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-release-master-nightly-4.18-e2e-rosa-sts-ovn/1856870032659714048

[neisw]

/lgtm

[openshift-ci[bot]]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: neisw, stbenjam

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/origin/blob/master/OWNERS)~~ [neisw,stbenjam] 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]

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

In response to [this](https://github.com/openshift/origin/pull/29296): >Some ephemeral pods in rosa namespaces like openshift-sre-pruning are triggering failures that didn't have per-pod exceptions, just skip examining these namespaces alltogether. > >Example: >https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-release-master-nightly-4.18-e2e-rosa-sts-ovn/1856870032659714048 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.

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 3fd5f626eca7ac52862a5331d9bce18bd771fa7f and 2 for PR HEAD 6fb63478aaaab808194ac3a49dae4b4cf967b05e in total

[openshift-trt-bot]

Job Failure Risk Analysis for sha: 6fb63478aaaab808194ac3a49dae4b4cf967b05e

Job Name

Failure Risk

pull-ci-openshift-origin-master-e2e-aws-ovn-edge-zones

High [bz-kube-apiserver][invariant] alert/KubeAPIErrorBudgetBurn should not be at or above info This test has passed 100.00% of 4 runs on jobs ['periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-edge-zones' 'periodic-ci-openshift-release-master-nightly-4.17-e2e-aws-ovn-edge-zones'] in the last 14 days. Open Bugs SNO error rate for alert/KubeAPIErrorBudgetBurn should not be at or above info

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 3fd5f626eca7ac52862a5331d9bce18bd771fa7f and 2 for PR HEAD 6fb63478aaaab808194ac3a49dae4b4cf967b05e in total

[stbenjam]

/override ci/prow/e2e-aws-ovn-edge-zones

Unrelated

[stbenjam]

/skip

[openshift-ci[bot]]

@stbenjam: Overrode contexts on behalf of stbenjam: ci/prow/e2e-aws-ovn-edge-zones

In response to [this](https://github.com/openshift/origin/pull/29296#issuecomment-2477121186): >/override ci/prow/e2e-aws-ovn-edge-zones > >Unrelated 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.

[openshift-ci[bot]]

@stbenjam: 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-aws-ovn-single-node	6fb63478aaaab808194ac3a49dae4b4cf967b05e	link	false	/test e2e-aws-ovn-single-node
ci/prow/e2e-metal-ipi-ovn	6fb63478aaaab808194ac3a49dae4b4cf967b05e	link	false	/test e2e-metal-ipi-ovn
ci/prow/e2e-aws-csi	6fb63478aaaab808194ac3a49dae4b4cf967b05e	link	false	/test e2e-aws-csi
ci/prow/e2e-aws-ovn-single-node-upgrade	6fb63478aaaab808194ac3a49dae4b4cf967b05e	link	false	/test e2e-aws-ovn-single-node-upgrade
ci/prow/e2e-aws-ovn-kube-apiserver-rollout	6fb63478aaaab808194ac3a49dae4b4cf967b05e	link	false	/test e2e-aws-ovn-kube-apiserver-rollout
ci/prow/e2e-agnostic-ovn-cmd	6fb63478aaaab808194ac3a49dae4b4cf967b05e	link	false	/test e2e-agnostic-ovn-cmd
ci/prow/e2e-aws-ovn-single-node-serial	6fb63478aaaab808194ac3a49dae4b4cf967b05e	link	false	/test e2e-aws-ovn-single-node-serial
ci/prow/e2e-metal-ipi-ovn-kube-apiserver-rollout	6fb63478aaaab808194ac3a49dae4b4cf967b05e	link	false	/test e2e-metal-ipi-ovn-kube-apiserver-rollout

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

[ART PR BUILD NOTIFIER]

Distgit: openshift-enterprise-tests This PR has been included in build openshift-enterprise-tests-container-v4.19.0-202411142010.p0.gd86ecc9.assembly.stream.el9. All builds following this will include this PR.