WHY
RHOAM relies on PrometheusRules as part of its monitoring solution.

WHAT
Context: RHOAM currently creates a number of PrometheusRules(monitoring.coreos.com/v1) in the redhat-rhoam-observability Namespace.

Task 1: OBO will only recognize "monitoring.rhobs/v1" PrometheusRules. So we need to change all the PrometheusRules that RHOAM manages to be "monitoring.rhobs/v1" PrometheusRules CRs and not "monitoring.coreos.com/v1" PrometheusRules CRs.

Task 2: All of the PrometheusRules are created in the redhat-rhoam-observability Namespace which we are removing as part of the migration. So we need to move these PrometheusRules CRs to the redhat-rhoam-operator Namespace.

HOW
<Suggestions for how this may be solved. [Optional]

TESTS
<List of related tests>

DONE

• All PrometheusRules that RHOAM manages are changed to be "monitoring.rhobs/v1" CRs
• All PrometheusRules that were created in redhat-rhoam-observability are now created in redhat-rhoam-operator