feat(container): update image postgresql to v16.3.4

[renovate]

This PR contains the following updates:

Package	Update	Change
postgresql (source)	minor	16.2.5 -> 16.3.4

---

Release Notes

bitnami/charts (postgresql)

v16.3.4

• [bitnami/postgresql] Release 16.3.4 (#​31143)

v16.3.3

• [bitnami/postgresql] Release 16.3.3 (#​31133) (41671f2), closes #​31133

v16.3.2

• [bitnami/*] Fix typo in README (#​31052) (b41a51d), closes #​31052
• [bitnami/postgresql] Release 16.3.2 (#​31060) (1406ab1), closes #​31060

v16.3.1

• [bitnami/postgresql] Add Storage Class Configuration to Templates (#​30858) (b0d2c2e), closes #​30858

v16.3.0

• [bitnami/*] Add Bitnami Premium to NOTES.txt (#​30854) (3dfc003), closes #​30854
• [bitnami/postgresql] Detect non-standard images (#​30936) (ac96151), closes #​30936

---

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.

No specific security issues can be identified merely from the version bump in a Helm chart for PostgreSQL from 16.2.5 to 16.3.1 as depicted in the provided git diff. Version updates generally include security fixes, improvements, and new features which means upgrading could potentially resolve known vulnerabilities in the previous version.

However, it's critically important to review the release notes of PostgreSQL 16.3.1 to ensure no breaking changes or new, potentially insecure defaults are being introduced. This review step is external to what can be inferred from the diff directly.

Suggested Actions:

1. Review Release Notes: Before merging this change, carefully review the PostgreSQL 16.3.1 release notes for any security advisories, breaking changes, or other noteworthy modifications.
2. Test for Compatibility: Ensure that Mastodon and any dependent services are fully compatible with PostgreSQL 16.3.1. This includes running integration tests to confirm that the update does not introduce any regressions.
3. Database Backup: Always ensure that there's a comprehensive backup strategy in place before applying database upgrades. This allows you to restore the previous state in case of any unforeseen issues.
4. Monitor After Deployment: Observe the application and database performance and behavior closely after the upgrade. This helps in spotting any issues arising from the update early on.

If after reviewing the release notes and potential impact on the Mastodon application there are no concerns, then upgrading PostgreSQL as described in the diff can be deemed a suitable and possibly beneficial action.