Keycloak startupProbe disabled by default causes CrashLoopBackOff on fresh installs (bug)

The bundled Keycloak (Bitnami chart) ships with startupProbe.enabled: false by default, but its livenessProbe fires ~123s in — too short for a cold boot in most real environments. Result: a fresh install crash-loops before Keycloak ever finishes starting, with no clear indication of the actual cause from the pod logs. Suggested fix: enable startupProbe by default in the chart's own values (or at least document this prominently), since this affects any first-time deployer, not just AWS/EKS-specific setups.