[bitnami/postgresql-ha] Fix issue where user password is not set when a different username is provided

[migruiz4]

Description of the change

Fixes an issue where env variable POSTGRES_POSTGRES_PASSWORD was not being when global.posgresql.username/posgresql.username is set to a value different than postgres.

Although key postgresql-password is being automatically generated in the Secret, the password will never be set unless value posgresql.postgresPassword/global.posgresql.postgresPassword.

This PR makes it possible for users to use postgresql-ha chart where postgres user uses a random password.

Possible drawbacks

I'm not sure if this behavior was intentional, to force users to provide a password for user postgres and avoid risks of users losing the root user password on restarts.

Applicable issues

• fixes [bitnami/postgresql-ha] Standard postgresql-ha deployment fails when username/password are provided #24226

Checklist

• Chart version bumped in Chart.yaml according to semver. This is not necessary when the changes only affect README.md files.
• Variables are documented in the values.yaml and added to the README.md using readme-generator-for-helm
• Title of the pull request follows this pattern [bitnami/<name_of_the_chart>] Descriptive title
• All commits signed off and in agreement of Developer Certificate of Origin (DCO)

[fmulero]

LGTM

I don't see any problem right now. Users who already set postgresPassword shouldn't face any issue

[github-actions]

This Pull Request has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thank you for your contribution.

[github-actions]

Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Pull Request. Do not hesitate to reopen it later if necessary.

[8ball030]

can we please get this merged?
Theres like 3 issues which seem to be a subsequent downstream issue of this.