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>

docs/FIX_ENV_TRUNCATION.md

@@ -38,10 +38,20 @@ This script will:
 2. Use password: `admin123`
 3. You should be able to log in successfully
 
+## Known Issue: bcrypt Architecture
+
+Due to architecture differences (ARM vs x86), bcrypt may need to be rebuilt after container restart:
+
+```bash
+# Fix bcrypt after container restart
+docker exec minio-webui-backend-dev sh -c 'rm -rf /app/node_modules/bcrypt && cd /app && npm install bcrypt' && docker restart minio-webui-backend-dev
+```
+
 ## Troubleshooting
 
 If issues persist:
-1. Check that .env file exists and has proper quotes around values with special characters
+1. Check that .env file exists and has double dollar signs ($$) for escaping
 2. Ensure Docker containers were rebuilt: `docker compose -f docker-compose.dev.yml up -d --build`
 3. Check logs: `docker logs minio-webui-backend-dev`
-4. Run debug script: `./scripts/debug-auth.sh`
+4. Run debug script: `./scripts/debug-auth.sh`
+5. If bcrypt error occurs, run the fix command above