fix: Remap SeaweedFS ports to avoid conflicts on asgard

Port conflicts on asgard stack:
- 9333 → 8093 (SeaweedFS Master)
- 8080 → 8094 (SeaweedFS Volume)

Updated:
- docker-compose.yml
- README.md
- NPM-CONFIG.md

Final port allocation:
8090: Gitea HTTP
2222: Gitea SSH
8091: SeaweedFS Filer UI (cdn.corrosionmgmt.com)
8092: SeaweedFS S3 API
8093: SeaweedFS Master (internal)
8094: SeaweedFS Volume (internal)

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

infra/README.md

@@ -15,8 +15,8 @@
 - **Container**: `corrosion-cdn`
 - **Filer UI Port**: 8091 (primary CDN interface)
 - **S3 API Port**: 8092 (programmatic access)
-- **Master Port**: 9333 (admin/monitoring)
-- **Volume Port**: 8080 (internal storage)
+- **Master Port**: 8093 (admin/monitoring)
+- **Volume Port**: 8094 (internal storage)
 - **Purpose**: Map hosting, plugin packages, companion binaries, backups
 
 ## Deployment
@@ -56,7 +56,7 @@ docker compose up -d
 - **Gitea SSH**: ssh://git@git.corrosionmgmt.com:2222
 - **CDN Filer UI**: https://cdn.corrosionmgmt.com
 - **S3 API**: http://<asgard-ip>:8092 (internal only, no proxy)
-- **SeaweedFS Master**: http://<asgard-ip>:9333 (internal only, no proxy)
+- **SeaweedFS Master**: http://<asgard-ip>:8093 (internal only, no proxy)
 
 ## First-time Gitea Setup