1. Proposed title of this feature request
Replace the use of `user-workload-monitoring-config` ConfigMap with a custom resource [0]

2. What is the nature and description of the request?
Most of the Core OpenShift Operators use custom resources to represent the current state of the Operator.
The request here is to bring the OpenShift Monitoring Operator into alignment with this and provide a custom resources for performing configuration of the overall monitoring deployment in OpenShift. Specifically replacing the `user-workload-monitoring-config` ConfigMap.

3. Why does the customer need this? (List the business requirements here)
The customer requires performing changes to the OpenShift Monitoring configuration (user-workload-monitoring-config ConfigMap) using the OpenShift GitOps Operator. Alongside the GitOps Operator, the customer must use the OpenShift Advanced Cluster Manager, which also performs changes to the ConfigMap values.

As `ConfigMap.data` sections can hold unstructured data, there is currently an inability for both operators to control different sections of the same ConfigMaps' key-value data. This results in one of the Operators taking precedence.

The request here is for the OpenShift Monitoring Operator and it's sub-Operators to provide structured custom resource definitions to allow for configuration of the deployments in alignment with the other core OpenShift Operators.

4. List any affected packages or components.
OpenShift Monitoring

Resources:
[0] https://docs.openshift.com/container-platform/4.11/monitoring/enabling-monitoring-for-user-defined-projects.html