feat(container)!: Update image postgresql to v16

[renovate]

This PR contains the following updates:

Package	Update	Change
postgresql (source)	major	15.5.28 -> 16.2.1

---

Release Notes

bitnami/charts (postgresql)

v16.2.1

• [bitnami/postgresql] Release 16.2.1 (#​30463)

v16.2.0

• [bitnami/postgresql] feat: ✨ Add password update job (#​30444)

v16.1.2

• [bitnami/postgresql] Release 16.1.2 (#​30250)

v16.1.1

• [bitnami/postgresql] metrics.collectors applies to read replicas (#​30133) (696f113), closes #​30133

v16.1.0

• [bitnami/postgresql] Added support for namespaceOverride (#​30113)

v16.0.6

• [bitnami/postgresql] Release 16.0.6 (#​30069)

v16.0.5

• [bitnami/postgresql] Release 16.0.5 (#​30046) (a825e37), closes #​30046

v16.0.4

• [bitnami/postgresql] Release 16.0.4 (#​30013) (8435f88), closes #​30013

v16.0.3

• [bitnami/postgresql] Release 16.0.3 (#​29942)

v16.0.2

• [bitnami/postgresql] Release 16.0.2 (#​29938) (766c157), closes #​29938
• Update documentation links to techdocs.broadcom.com (#​29931) (f0d9ad7), closes #​29931

v16.0.1

• [bitnami/postgresql] Release 16.0.1 (#​29776)

v16.0.0

• [bitnami/postgresql] Release 16.0.0 (#​29723) (aeedc0e), closes #​29723

v15.5.38

• [bitnami/postgresql] Release 15.5.38 (#​29681) (105fcbb), closes #​29681

v15.5.37

• [bitnami/postgresql] Release 15.5.37 (#​29660) (45cada1), closes #​29660

v15.5.36

• [bitnami/postgresql] Release 15.5.36 (#​29640) (074e377), closes #​29640

v15.5.35

• [bitnami/postgresql] Release 15.5.35 (#​29610) (1f3717a), closes #​29610

v15.5.32

• [bitnami/postgresql] test: ✅ Improve reliability of ginkgo tests (#​29472) (c43177e), closes #​29472

v15.5.31

• [bitnami/postgresql] Release 15.5.31 (#​29404) (baf9a0f), closes #​29404

v15.5.30

• [bitnami/postgresql] collect metrics as postgres user (#​29201) (7240870), closes #​29201

v15.5.29

• [bitnami/postgresql] Release 15.5.29 (#​29330) (3c161f7), closes #​29330

---

Configuration

📅 Schedule: Branch creation - "on saturday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[jsaveker]

Here is an automated review from ChatGPT of this pull request.

There were no direct security issues that could be identified from the provided "git diff" snippet as it focuses on a version update for the PostgreSQL container within a Kubernetes deployment managed by Helm. However, updating to a new major version (from 15.x.x to 16.x.x) could introduce backward compatibility issues or might have significant changes that could indirectly affect the security of the deployments if not properly vetted or tested. It would be crucial to review the release notes of PostgreSQL version 16.0.1 to identify any breaking changes or specific security adjustments.

To ensure a secure upgrade, consider the following steps as markdown-formatted suggestions:

## Steps to Securely Upgrade PostgreSQL
1. **Review the PostgreSQL 16.0.1 Release Notes**: Before proceeding with the upgrade, carefully review the release notes of PostgreSQL 16.0.1 to understand any new features, deprecated functionalities, or removed features that could impact the existing setup.

2. **Check for Deprecated Features**: Verify if your current use of PostgreSQL relies on any features that are deprecated or removed in the new version. Plan necessary adjustments accordingly.

3. **Test the Upgrade in a Staging Environment**: Before rolling out the new version to production, deploy the upgrade in a controlled, staging environment. This helps in identifying and rectifying any issues that might not be evident through code review alone.

4. **Backup Existing Data**: Always ensure that there are robust, recent backups of your PostgreSQL databases before attempting an upgrade. This provides a rollback point in case of any issues.

5. **Monitor Application Logs and Performance**: After deploying the upgraded version to production, monitor application logs and database performance closely. Look out for any warnings, errors, or performance degradation that may indicate issues with the new database version.

Without specific details on the configuration and usage of PostgreSQL in this context, these preventative suggestions are aimed at mitigating potential risks associated with a major version upgrade. Always consider applying these best practices to minimize interruption and maintain the security and integrity of your applications and their data.