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/.env.prod.seaweedfs.split.example

@@ -129,13 +129,7 @@ SEAWEED_DATA=seaweed_data
 # The SeaweedFS image, pinned so a redeploy months from now brings up the same
 # one. All five SeaweedFS containers run it.
 # SEAWEED_IMAGE=chrislusf/seaweedfs:4.45
-# The S3 port is published on loopback only — the stack reaches the gateway over
-# the compose network, 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 publish no host port at all. The admin UI below
+# The S3 gateway, master, volume and filer 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, so it stays on the compose network. Reach the
 # others with `docker compose exec`.