In MON-2792 we tried to gather requirements for clients that create monitoring related resources. While we will push hard to change clients to the rhobs api group there is a chance not all components can rename the resources in time or at all.

For this reason we want to at least map out the technical solution on how to translate between some monitoring resources of the same name but different api groups or find technical issues early.

This should be implemented as an additional controller of observability operator. In order to not depend on a specific module version for the coreos api group, it might make sense to fetch and marshal these resources into an unstructured object and travers the resulting dictionary to create the rhobs group resource.

Starting with one resource (ServiceMonitor) seems ideal. If we need to implement this productively we'll need other resources as well (certainly PodMonitor and PrometheusRule), so while implementing a PoC for ServiceMonitor will suffice it'd be good to get an idea how to implement the translation for additional resources (same controller, one controller per resource, ...).