Docker, Docker-AIO: private registry, data volumes set from .env

Images now default to the registry 10.2.1.10:5500/admin instead of
ghcr.io/dariuszjaniak, in the compose files, the .env examples and the
READMEs.

Each data volume's source comes from .env: WARP_DATA_VOLUME,
WARP_POSTGRES_VOLUME, SEAWEED_DATA_VOLUME and SEAWEED_ADMIN_VOLUME.
Empty keeps the named volume; a host path bind-mounts that directory,
which must be writable by UID 10001 where the homeserver or the AIO
container uses it. Each .env example lists the ones its compose file
mounts.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Docker-AIO/.env.postgresql.prod.example

@@ -22,9 +22,15 @@ WARP_WEB_PORT=8080
 
 # The image is pulled from $WARP_REGISTRY/warp-aio-postgresql at this tag.
 # Pin a release in production.
-WARP_REGISTRY=ghcr.io/dariuszjaniak
+WARP_REGISTRY=10.2.1.10:5500/admin
 WARP_VERSION=latest
 
+# Where the data lives. Empty keeps the named volume in brackets; a
+# host path (starting with . or /) bind-mounts that directory instead.
+# The container runs as UID 10001, so its directory must be writable by it.
+# The homeserver's /data (warp-data).
+WARP_DATA_VOLUME=
+
 # ------------------------------------------------------------------- aio
 
 # false runs the container without the admin panel or the web client.