[Improvement-17560][Helm] Update Bitnami chart versions for PostgreSQL, MySQL and Zookeeper

[zhan7236]

What is the purpose of the pull request

This PR performs a comprehensive update of the DolphinScheduler Helm charts to ensure compatibility with the new versions of Bitnami charts, as outlined in issue #17560.

The main changes include:

1. Migrating from bitnamilegacy/* images to official bitnami/* images
2. Updating Helm chart dependency versions
3. Adapting configuration formats to match new Bitnami chart requirements

Brief change log

Chart Version Updates:

• Update PostgreSQL chart from 10.3.18 to 12.1.5
• Update Zookeeper chart from 11.4.11 to 13.8.7
• Update MySQL chart from 9.4.1 to 9.23.0
• Update MinIO chart from 11.10.13 to 12.13.2

Image Updates (migrating from bitnamilegacy to bitnami):

• PostgreSQL: bitnamilegacy/postgresql:11.11.0 → bitnami/postgresql:15.1.0-debian-11-r12
• Zookeeper: bitnamilegacy/zookeeper:3.8.4 → bitnami/zookeeper:3.9.3-debian-12-r21
• MySQL: bitnamilegacy/mysql:8.0.31 → bitnami/mysql:8.0.36-debian-12-r8
• MinIO: bitnamilegacy/minio:2022.10.29 → bitnami/minio:2023.12.23-debian-11-r3

Configuration Format Updates:

• PostgreSQL: Migrate from postgresqlUsername/Password/Database to auth.username/password/database
• PostgreSQL: Migrate persistence.* to primary.persistence.*
• Update _helpers.tpl to use new PostgreSQL auth config structure
• Update keda-autoscaler-worker.yaml to use new PostgreSQL auth config

Repository Migration:

• Migrate all dependencies from https://raw.githubusercontent.com/bitnami/charts/archive-full-index/bitnami to https://charts.bitnami.com/bitnami
• Remove outdated comments about Bitnami repository changes

Verify this pull request

This PR has been verified by:

• helm dependency update - All charts downloaded successfully
• helm template test . - Template rendering works correctly

Related Issues

Closes #17560 Closes #17561 Closes #17562 Closes #17563 Closes #17564

[sonarqubecloud[bot]]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[Mrhs121]

According to Bitnami’s official notice, after 28 Aug 2025:

• docker.io/bitnami will only contain a hardened, latest-tag-only community subset; no historical versions will be kept there.
• ZooKeeper, MinIO, MYSQL and any image not in that subset will disappear from the free catalog. Currently, zookeeper, minio and mysql images or tags cannot be retrieved in the bitnamisecure repository and bitnami repository
• Existing tags (including ZooKeeper/MinIO/Mysql) are moved to docker.io/bitnamilegacy but receive no further updates or security fixes.

@Gallardot I think it's not appropriate to directly replace all of repository:bitnamilegacy with repository:bitnami here

[Gallardot]

According to Bitnami’s official notice, after 28 Aug 2025:

• docker.io/bitnami will only contain a hardened, latest-tag-only community subset; no historical versions will be kept there.
• ZooKeeper, MinIO, MYSQL and any image not in that subset will disappear from the free catalog. Currently, zookeeper, minio and mysql images or tags cannot be retrieved in the bitnamisecure repository and bitnami repository
• Existing tags (including ZooKeeper/MinIO/Mysql) are moved to docker.io/bitnamilegacy but receive no further updates or security fixes.

@Gallardot I think it's not appropriate to directly replace all of repository:bitnamilegacy with repository:bitnami here

Yes, it's not just about replacing the docker image. Helm charts themselves also have some configurations that need to be adapted.