Description of problem:

When disabling user-workload monitoring on a spoke, we leave the configmap "user-workload-monitoring-config" in place with the alerting config pointing to the spoke. While this has no functional impacts, we should ensure we clean up correctly.

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

ACM 2.14

How reproducible:

Always

Steps to Reproduce:

1. Setup a spoke and enable UWL monitoring by editing the CMO configmap

data:
  config.yaml: |
    enableUserWorkload: true

1. See that the `user-workload-monitoring-config` configmap in namespace `openshift-user-workload-monitoring` exists and includes configuration to send alerts to the hub alertmanager
2. Disable UWL monitoring on the spoke, by editing the CMO configmap
3.  

Actual results:

See that the `user-workload-monitoring-config` configmap in namespace `openshift-user-workload-monitoring`is unchanged and still points to ACM alertmanager.

Expected results:

The configmap should be reset/deleted

Additional info: