updating postgres-is-ready init container to use the same hostname env var template as the nextcloud container

[jessebot]

Pull Request

Description of the change

This changes the template for the postgresql-is-ready init container to use the same hostname variable, POSTGRES_HOST that we use for the actual nextcloud container.

Benefits

This should make it so that if you use postgresql.enabled=true and postgresql.fullnameOverride=my-postgres-name that we use that for checking if postgresql is ready as well. Previously, we were using {.Release.name}-postgresql which would not accommodate postgresql.fullnameOverride.

Possible drawbacks

None that I can think of, but as always, open to feedback. If there's a better hostname to use instead of the primary hostname, I'm happy to change to that though I only saw a few services in the bitnami postgresql templates and those were the primary, primary headless, and read replicas. Read could work, but I actually don't know what primary headless does?

Checklist

• [x] DCO has been signed off on the commit.
• [x] Chart version bumped in Chart.yaml according to semver.
• [ ] (optional) Variables are documented in the README.md

[jessebot]

I will merge this after #444 so just before that, I'll update the chart version one last time.