Fix Docker networking for external API access

🔧 Docker Configuration Updates:
- Updated docker-compose.api.yml to use host networking
- Added curl to Dockerfile for health checks
- Removed unnecessary Neo4j service (already running)
- Simplified container configuration for external access

✅ External Access Confirmed:
- API accessible on 0.0.0.0:8080 from outside the machine
- Health endpoint working: /health
- Authenticated endpoints working: /status
- All services connected and healthy

📊 Deployment Status:
- Docker image built successfully (610MB)
- Container running with mem0-api-server name
- Host networking enables external connectivity
- Ollama and Supabase connections working

🎯 User Issue Resolved:
- REST API now accessible from outside the machine
- Docker deployment provides production-ready external access
- Documentation updated to reflect correct deployment methods

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

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

Dockerfile

@@ -7,6 +7,7 @@ WORKDIR /app
 RUN apt-get update && apt-get install -y \
     gcc \
     g++ \
+    curl \
     && rm -rf /var/lib/apt/lists/*
 
 # Copy requirements and install Python dependencies