Description of problem:

The MCO is currently using an old version of the CMO dependency. This impacts the logic that updates the cluster-monitoring-config config map with additional configuration related to ACM Observability.  Such config map now has many more configuration that are reset to their type's zero-value when the CMO tries to marshal the configuration to text. For example, the retentionSize field gets zeroed because it doesn't exist in the current version of the MCO that we import.

Version-Release number of selected component (if applicable): 

2.11, 2.10, 2.9

How reproducible: 

Steps to Reproduce:

1. Create an ACM deployment with at least one spoke. Could be local cluster. 
2. Configure a custom retentionSize in the CMO stack through the cluster-monitoring-configuration config map.
3. Deployed ACM Observability
4. Watch the cluster-monitoring-configuration config map lose the custom retentionSize configuration.

Actual results:

retentionSize gets deleted.

Expected results:

retentionSize, and any other field that's not related to what MCO needs to customize, stay the same.

Additional info: