docs: Remove obsolete volume_mode references from documentation

The volume_mode parameter is no longer used since workflows now upload files to MinIO storage instead of mounting volumes directly. This commit removes all references to volume_mode from:

- Backend API documentation (README.md)
- Tutorial getting started guide
- MCP integration guide
- CLI AI reference documentation
- SDK documentation and examples
- Test project documentation

All curl examples and code samples have been updated to reflect the current MinIO-based file upload approach.

docs/docs/how-to/mcp-integration.md

@@ -83,7 +83,6 @@ You should see status responses and endpoint listings.
   "parameters": {
     "workflow_name": "infrastructure_scan",
     "target_path": "/path/to/your/project",
-    "volume_mode": "ro",
     "parameters": {
       "checkov_config": {
         "severity": ["HIGH", "MEDIUM", "LOW"]
@@ -183,7 +182,7 @@ curl http://localhost:8000/workflows/
 ```bash
 curl -X POST http://localhost:8000/workflows/infrastructure_scan/submit \
   -H "Content-Type: application/json" \
-  -d '{"target_path": "/your/path", "volume_mode": "ro"}'
+  -d '{"target_path": "/your/path"}'
 ```
 
 ### General Support

docs/docs/reference/cli-ai.md

@@ -136,7 +136,6 @@ FuzzForge supports the Model Context Protocol (MCP), allowing LLM clients and AI
   "parameters": {
     "workflow_name": "infrastructure_scan",
     "target_path": "/path/to/your/project",
-    "volume_mode": "ro",
     "parameters": {
       "checkov_config": {
         "severity": ["HIGH", "MEDIUM", "LOW"]
@@ -193,7 +192,7 @@ FuzzForge supports the Model Context Protocol (MCP), allowing LLM clients and AI
   `curl http://localhost:8000/workflows/`
 
 - **Scan Submission Errors:**
-  `curl -X POST http://localhost:8000/workflows/infrastructure_scan/submit -H "Content-Type: application/json" -d '{"target_path": "/your/path", "volume_mode": "ro"}'`
+  `curl -X POST http://localhost:8000/workflows/infrastructure_scan/submit -H "Content-Type: application/json" -d '{"target_path": "/your/path"}'`
 
 - **General Support:**
   - Check Docker Compose logs: `docker compose logs fuzzforge-backend`

docs/docs/tutorial/getting-started.md

@@ -186,8 +186,7 @@ For local files, you can use the upload endpoint:
 # Create tarball and upload
 tar -czf project.tar.gz /path/to/your/project
 curl -X POST "http://localhost:8000/workflows/security_assessment/upload-and-submit" \
-     -F "file=@project.tar.gz" \
-     -F "volume_mode=ro"
+     -F "file=@project.tar.gz"
 
 # Check status
 curl "http://localhost:8000/runs/{run-id}/status"