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/docker-compose.seaweedfs.yml

@@ -37,10 +37,7 @@ services:
     volumes:
       # From here on the attachments live here, not on pb_data.
       - seaweed_data:/data
-    ports:
-      # The stack reaches the gateway over the compose network; this is here so
-      # `aws s3 ls --endpoint-url http://localhost:8333` works while developing.
-      - "${SEAWEED_S3_PORT:-8333}:8333"
+    # No published port: the stack reaches the gateway over the compose network.
     healthcheck:
       test: ["CMD-SHELL", "wget -qO- http://127.0.0.1:9333/cluster/status || exit 1"]
       interval: 10s