SeaweedFS: S3 gateway on the compose network only

PocketBase reaches the gateway over the compose network (or inside the
AIO container), so publishing 8333 on the host only made a second
SeaweedFS stack fail with "port is already allocated". Drop the binding
and SEAWEED_S3_BIND/SEAWEED_S3_PORT.

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

Docker-AIO/.env.prod.seaweedfs.split.example

@@ -97,14 +97,9 @@ PB_S3_BUCKET=drivervault
 # docker-compose.prod.seaweedfs.yml are interchangeable on the same volume, with
 # nothing to migrate either way.
 SEAWEED_DATA=seaweed_data
-# The S3 port is published on loopback only — PocketBase reaches the gateway
-# inside the container, and this is for tools like aws-cli. Set
-# SEAWEED_S3_BIND=0.0.0.0 to expose it to other hosts, and mean it.
-# SEAWEED_S3_BIND=127.0.0.1
-# SEAWEED_S3_PORT=8333
-#
-# The master, volume and filer listen on the container's loopback and publish
-# no host port at all. The admin UI below shows what they would: the volume
+# The S3 gateway publishes no host port: PocketBase reaches it inside the
+# container. The master, volume and filer listen on the container's loopback
+# and publish no host port at all. The admin UI below shows what they would: the volume
 # server in particular serves file content by id with no authentication. Reach
 # them with `docker compose exec drivervault wget -qO- http://127.0.0.1:9333/...`
 # (volume 8081, filer 8888).
@@ -123,7 +118,7 @@ SEAWEED_ADMIN_PASSWORD=
 # Optional view-only login.
 SEAWEED_ADMIN_READONLY_USER=
 SEAWEED_ADMIN_READONLY_PASSWORD=
-# Bound to localhost by default, the same call SEAWEED_S3_BIND makes: storage
+# Bound to localhost by default: storage
 # plumbing, not one of the app's own panels. On a remote host that means
 # unreachable — set 0.0.0.0 and put it behind a reverse proxy.
 SEAWEED_ADMIN_BIND=127.0.0.1