Add Docker Compose deployment for Hermes memory

[NianJiuZst]

Summary

Adds a Docker Compose deployment path for the existing Hermes + memory-tencentdb Gateway image.

This PR keeps the existing Dockerfile.hermes as the image build source, and adds the missing compose-level deployment layer:

• docker/opensource/compose.yaml for build/start/restart/port/volume/env wiring
• docker/opensource/.env.example for required model settings and optional Gateway security settings
• README and Docker README updates that make Compose the recommended greenfield Hermes deployment path while preserving the existing docker run fallback

Scope

This is a deployment improvement for the existing Hermes path. It does not introduce a new adapter abstraction and does not change the Gateway or memory pipeline runtime logic.

The resulting flow is:

cd docker/opensource
cp .env.example .env
# fill MODEL_API_KEY
docker compose up -d --build
curl http://localhost:8420/health
docker compose exec hermes-memory hermes

Notes

• The compose service persists /opt/data through the hermes_data volume.
• MODEL_API_KEY is required at compose config time.
• Optional TDAI_GATEWAY_API_KEY and TDAI_CORS_ORIGINS are wired through for protected/non-local deployments.
• Gateway logs are documented as container stdout/stderr via docker compose logs -f hermes-memory.

Validation

• docker-compose --env-file .env.example -f compose.yaml config
• YAML parse check for docker/opensource/compose.yaml
• git diff --check

[Maxwell-Code07]

Thank you for your contribution and interest! We will schedule an internal review of your code and get back to you soon.