Upgrade bitnami/postgresql subchart to 13.2.24

[dnskr]

The PR upgrades postgresql dependency of Airflow helm chart:

• bitnami/postgresql subchart upgraded from 12.10.0 to 13.2.24
• PostgreSQL upgraded from PostgreSQL 11 to PostgreSQL 16.1.0 (default in bitnami/postgresql:13.2.24)

The change requires bitnami/postgresql subchart users (not intended for production) to perform manual major version upgrade using pg_dumpall or pg_upgrade.

closes: #34817

---

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in newsfragments.

[hussein-awala]

I will check the failure in bandit check

[hussein-awala]

it was fixed by #36162

[dnskr]

Rebased onto main branch to include fix #36169.

[Taragolis]

I think it is better use specific major Postgres version here, rather than use default from bitnami/postgres subchart.

  image:
    tag: "16"

16 - referenced to the latest minor version of bitnami/postgresql of Postgres 16, it is in opposite of 16.1.0-debian-11-r15 which are referenced to the specific major.minor version

[dnskr]

Thank you for the review.
There is a good practice to use specific version rather than any sort of latest version as far as I know. Specific version provides better guarantees for deployment to be reproduceable and clear expectations on what exactly should be deployed:

1. Two bitnami/postgresql deployments with {{ .Values.image.tag }} = 16 might run different database versions. For instance, today it deploys 16.1.0-debian-11-r15, but few days ago 16.1.0-debian-11-r13 was deployed with the same values.yaml file.
2. The deployment with {{ .Values.image.tag }} = 16 not necessarily runs latest 16 version. For instance, because the chart was deployed a week ago when 16.1.0-debian-11-r15 didn't exist.
3. Fresh deployment with {{ .Values.image.tag }} = 16 not necessarily runs latest 16 version, because docker image with tag 16 might be presented in host from previous or parallel deployments.

Also, default value from bitnami/postgres was used before the #29207 where 11 version was pinned to resolve the upgrade issue temporary.

[Taragolis]

Differences between minor version of Postgres is a bug fixes include security one, data files are binary compatible between same major version.

So if only pin to the specific version then all users who doesn't care about specify version they would be get one of the first release of 16 Postgres, without fixes.

[Taragolis]

BTW, this only my suggestion, but not strong opinion

[dnskr]

I see your point. Let's see what others think.

[potiuk]

I think it's fine.. Postrgres chart is only used for testing/dev so we can get the default one.

[dnskr]

@potiuk @jedcunningham Could you please have a look at the changes?
It would be great if you can review it, because you both were involved in the previous changes and discussions about the issue.

[potiuk]

I think it's fine.. Postrgres chart is only used for testing/dev so we can get the default one.