Rook incorrectly creates new MON deployments during maintenance about component-rook-ceph

[simu]

After fixing the misconfiguration on the affected clusters (reduced health check timeout and interval), we've not had any issues with mons getting replaced when they shouldn't. Since we don't manage the field spec.healthCheck.daemonHealth.mon at all and rely on the operator's default values, ArgoCD won't revert custom changes which are applied when replacing storage nodes according to the documentation in https://kb.vshn.ch/oc4/how-tos/cloudscale/replace-storage-node.html#_remove_the_old_mon

We should consider having a default value for the field in the configuration rendered by the component, so that ArgoCD will clean up such changes automatically when sync gets enabled again after a manual operation.