OperatorConfig management

Is it possible to have a better way to manage OperatorConfig? Possibly with a config map or a custom resource similar to a `PodMonitoring` configuration.

Manually editing the yaml as suggested by the documentation isn't ideal.

Currently I apply changes to OperatorConfig across my environments using `kubectl patch` with terraform but this method isn't great either. I recently had an issue with too many metrics being scraped as I had enabled `kubeletScraping` for testing, after I removed the `kubeletScraping` config from my local yaml file I apply with `kubectl patch` it did not remove the config itself from kubernetes.