#4695: Fixed the default CLI image to use published GHCR image

Updates docker-compose to use the published GHCR image instead of the local moltbot image. This aligns the default CLI setup with the documented installation flow. <!-- greptile_comment --> <h2>Greptile Overview</h2> <h3>Greptile Summary</h3> This PR updates `docker-compose.yml` to stop defaulting to a locally-built image and instead default to a published GHCR image, aligning the compose-based CLI/gateway workflow with the documented install flow. It also consolidates the previous `openclaw-gateway` + `openclaw-cli` split into a single `clawdbot` service that runs `node dist/index.js gateway ...` and enables interactive TTY settings. <h3>Confidence Score: 3/5</h3> - This PR is reasonably safe to merge, but the compose changes can cause surprising behavior changes for existing users. - The change is limited to `docker-compose.yml`, but it switches to a moving `:main` container tag and renames an expected gateway token env var; both can break existing setups or make behavior non-reproducible without additional documentation or pinning. - docker-compose.yml <!-- greptile_other_comments_section --> _{(3/5) Reply to the agent's comments like "Can you suggest a fix for this @greptileai?" or ask follow-up questions!} **Context used:** - Context from `dashboard` - CLAUDE.md ([source](https://app.greptile.com/review/custom-context?memory=fd949e91-5c3a-4ab5-90a1-cbe184fd6ce8)) - Context from `dashboard` - AGENTS.md ([source](https://app.greptile.com/review/custom-context?memory=0d0c8278-ef8e-4d6c-ab21-f5527e322f13)) <!-- /greptile_comment -->