fix: Resolve mc config permission error and add MinIO setup documentation

- Replace read-only host mount with dedicated Docker volume for mc config
- Add init-mc-config.sh to initialize mc configuration with proper permissions
- Create setup-mc-alias.sh script to configure MinIO connection
- Add comprehensive MINIO_SETUP.md documentation
- Update docker-compose.dev.yml to use mc-config volume
- Update Dockerfile to run mc config initialization
- Document bcrypt architecture workaround in FIX_ENV_TRUNCATION.md

The mc client can now write to its configuration directory, resolving
the "permission denied" error when connecting to MinIO servers.

🤖 Generated with [Claude Code](https://claude.ai/code)

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

docker-compose.dev.yml

@@ -1,5 +1,3 @@
-version: '3.8'
-
 # Development docker-compose file
 # This configuration runs frontend and backend on custom ports without SSL/nginx proxy
 # Usage: docker compose -f docker-compose.dev.yml up
@@ -27,8 +25,7 @@ services:
       - ./backend/package-lock.json:/app/package-lock.json
       - backend-logs:/app/logs
       - backend-temp:/app/temp
-      - backend-node-modules:/app/node_modules
-      - ~/.mc:/home/node/.mc:ro
+      - mc-config:/home/node/.mc
     depends_on:
       - redis
     networks:
@@ -78,7 +75,7 @@ volumes:
     driver: local
   backend-temp:
     driver: local
-  backend-node-modules:
+  mc-config:
     driver: local
 
 networks: