Delete the openshift-monitoring/monitoring-plugin-cert secret, SCO will re-create a new one with different content

- monitoring-plugin is still using the old cert content.
- If the cluster doesn't show much activity, the hash may take time to be updated.

CMO should detect that exact change and run a sync to  recompute and set the new hash.

- We shouldn't rely on another changeto trigger the sync loop.
- CMO should maybe watch that secret? (its name isn't known in advance).