feat(deployment): add Dokploy Compose setup and guide

[XDR-SAM]

Deploying OpenDots through Dokploy currently requires adapting the local Compose setup and working out the app build target, domain routing, environment injection, and persistent storage. This adds a dedicated configuration and guide so users can select the repository, set their environment and HTTPS domain once, and deploy through Dokploy.

• Add compose.dokploy.yml using the existing Dockerfile's app target, internal port 4310, a named SQLite data volume, and a web-server health check.
• Require OWNER_TOKEN and APP_ORIGIN; leave AI and optional integrations unconfigured until credentials are supplied.
• Add an environment template and instructions for Dokploy's native domain routing, HTTPS, AI setup, and storage backups, linked from README and the setup guide.

No Dokploy-specific setup or related PR/issue was found in upstream before preparing this contribution. This is a documented Dokploy deployment path; it does not register a one-click template in Dokploy's template catalog.

Validation on Node.js 24.14.1:

• Docker Compose configuration validation passed.
• Formatting, lint, typecheck, production build, and git diff --check passed.
• npm test -- --maxWorkers=2: 301/302 passed; one existing telemetry subprocess test exceeded the default 5-second timeout (related upstream PR test: give telemetry probes their subprocess budget #120).
• npm test -- --maxWorkers=2 --testTimeout=20000: all 302 tests across 48 files passed. No test source or timeout configuration was changed.

A live Dokploy deployment, container image build, and connected AI responses were not verified; the local Docker daemon is not running. The health check verifies HTTP availability only.