#17916: [ fix ] : correct config directory path during onboarding

Changed the target configuration directory from the legacy /home/node/.clawdbot to /home/node/.openclaw. Fixed #17524 Change Type [x] Bug fix [ ] Feature [ ] Refactor [ ] Docs [ ] Security hardening [x] Chore/infra Before: - CLI output: Config: .../.clawdbot/moltbot.json (Host dir empty). After: - CLI output: Config: .../.openclaw/moltbot.json (Host dir populated). <!-- greptile_comment --> <h3>Greptile Summary</h3> Added `OPENCLAW_STATE_DIR=/home/node/.openclaw` environment variable to both Docker services (`openclaw-gateway` and `openclaw-cli`). This ensures the application correctly uses the `.openclaw` directory instead of potentially falling back to legacy `.clawdbot` paths during onboarding. - Sets explicit state directory path for Docker containers - Aligns with existing volume mounts that already use `/home/node/.openclaw` - Fixes config path display issue reported in #17524 <h3>Confidence Score: 5/5</h3> - This PR is safe to merge with minimal risk - The change explicitly sets an environment variable that was previously undefined, ensuring consistent behavior. The code already has fallback logic (`resolveConfigDir` in `src/utils.ts:315`) that honors `OPENCLAW_STATE_DIR`, and the volume mounts already point to `/home/node/.openclaw`. This is a straightforward bug fix with no breaking changes. - No files require special attention _{Last reviewed commit: 137c199} <!-- greptile_other_comments_section --> _{(2/5) Greptile learns from your feedback when you react with thumbs up/down!} <!-- /greptile_comment -->