Pin PostgreSQL version in `*-postgres` templates about templates HOT 2 OPEN

Thank you for creating the issue and explaining the drawbacks of defaulting to the latest tag for postgres image.

The suggestion to allow users to override the tag (similar to imageVarient) makes sense. But we still need to have a default. I am afraid if a tag like 16-alpine can be the new default instead of latest, since that will hard pin the image and would never receive newer major versions unless we manually modify the template. Any thoughts around that?

from templates.

I think it would be good default, at least a better one. In perspective, pinned version in template would need to be updated every year around September/October when new major version is being released to match.
Pinned version also simplifies upgrading to latest minor version by rebuild (not sure if pull is set to always during them, docker pull postgres:16-alpine can be run previously to be safe).
Similarly if developer would need new version to utilize newly added features or simply upgrade it with persisting data still stays manual but more controllable.

from templates.