Enhance MySQL deployment configuration in Helm chart

[saadqbal]

• Added init containers for setting up MySQL data and logs with appropriate permissions.
• Increased resource requests and limits for memory and CPU to improve performance.
• Introduced startup, liveness, and readiness probes for better container health management.
• Updated security context for containers to ensure proper access control.

---

Note

Medium Risk
Moderate risk because it changes runtime behavior of the MySQL pod (startup gating, health checks, and filesystem permissions) and increases CPU/memory limits, which can affect scheduling and rollout stability.

Overview
Updates the mysql-client Helm Deployment to better handle volume permissions by adding a pod securityContext (fsGroup) and new root-run init container to create/chown /var/lib/mysql, plus adjusting the existing logs init container to run as root.

Increases container resource limits (512Mi→1Gi, 500m→1000m) and adds a startupProbe while reducing livenessProbe/readinessProbe initial delays to 0 so startup health is gated by the startup probe. Helm unit tests are updated to match the new memory limit.

^{Written by Cursor Bugbot for commit 190dd81. This will update automatically on new commits. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}