fix(redis-ha): hostPath chown init container must run as root

[DandyDeveloper]

Problem

Closes #396

When hostPath.chown=true, the hostpath-chown init container was inheriting the pod's containerSecurityContext via the compatibility.renderSecurityContext helper. This meant it ran with runAsNonRoot: true and runAsUser: 1000, causing chown to fail with "Permission denied" — you cannot change file ownership as a non-root user on a host-mounted directory.

Additionally, the chown command only set the user portion of the ownership (runAsUser), leaving the group ownership unchanged and not matching the pod's fsGroup.

Fix

1. Override securityContext for this init container only — set runAsUser: 0 and runAsNonRoot: false explicitly, so the hostpath-chown init container runs as root (required to chown a host-mounted path). All other containers are unaffected and continue to use the non-root containerSecurityContext.

2. Set uid:gid ownership — change the chown argument from "{{ .Values.containerSecurityContext.runAsUser }}" to "{{ .Values.containerSecurityContext.runAsUser }}:{{ .Values.securityContext.fsGroup }}" so both user and group ownership are set correctly, matching the pod-level fsGroup (default: 1000) used at runtime.

Changes

charts/redis-ha/templates/redis-ha-statefulset.yaml

• Replace inherited securityContext with explicit runAsUser: 0 / runAsNonRoot: false for the hostpath-chown init container
• Expand chown target from uid to uid:gid