Fix: Ensure ConfigMap and StatefulSet updates are applied during operator upgrades

[Mangaal]

What type of PR is this?
This PR fixes an issue where updates to the argocd-redis-ha-configmap, argocd-redis-ha-health-configmap, and the StatefulSet argocd-redis-ha-server were not being reflected during OpenShift GitOps operator upgrades.

The current code missed checking for changes in:

• The data field of argocd-redis-ha-configmap and argocd-redis-ha-health-configmap.
• The env variables in the StatefulSet argocd-redis-ha-server.

As a result, changes introduced in higher versions of the operator were not applied unless the config maps and StatefulSet were manually deleted or the .spec.ha.enabled field was toggled in the ArgoCD Custom Resource (CR). This PR ensures these changes are correctly detected and applied.

This PR:
Adds logic to check for changes in the argocd-redis-ha-configmap and argocd-redis-ha-health-configmap data fields during operator upgrades.
Includes validation for the env variables in the argocd-redis-ha-server StatefulSet to ensure updates are reflected.
Ensures that any required updates are applied automatically without manual intervention.

/kind bug

Steps to reproduce the issue:

• Install OpenShift GitOps Operator v1.12.0 on an OCP 4.16.4 cluster.
• Create an ArgoCD instance with .spec.ha.enabled = true.
• Upgrade the operator to v1.14.0, v1.14.1, and v1.14.2.
• Observe that the argocd-redis-ha-configmap and argocd-redis-ha-health-configmap are not updated as expected.
• Delete the config maps manually, and observe that they are recreated correctly but result in AUTH errors.
• Toggle the .spec.ha.enabled field to fix the issue.

[svghadi]

Can we add a unit test to check configmap reconciliation? Create the cm resource using reconcileRedisHAHealthConfigMap function, modify the created configmap resource and run the reconcileRedisHAHealthConfigMap again to ensure the values are reset to default