#12694: Devin/1770645191 add elizaos adapter

<!-- greptile_comment --> <h2>Greptile Overview</h2> <h3>Greptile Summary</h3> This PR adds `@elizaos/openclaw-adapter` as a new root dependency, introduces a GitHub Actions workflow to periodically merge upstream `openclaw/openclaw` into this fork, and changes gateway locking behavior to allow running multiple gateway instances by default (behind a new `OPENCLAW_ENFORCE_SINGLE_GATEWAY=1` opt-in). The main integration point with the existing codebase is `src/infra/gateway-lock.ts`, which is used to prevent multiple gateway processes from concurrently operating on the same machine/resources. The new workflow touches repo maintenance rather than runtime behavior, and the dependency change affects the install graph via `package.json`/`pnpm-lock.yaml`. <h3>Confidence Score: 2/5</h3> - Not safe to merge as-is due to CI/test stability and workflow correctness concerns. - Score is driven by a functional behavior change in `acquireGatewayLock` that disables the existing test guard by default (likely causing nondeterministic test failures), plus a sync workflow that can proceed after a failed merge and a lockfile diff that includes unrelated resolution churn. - src/infra/gateway-lock.ts, .github/workflows/sync-upstream.yml, pnpm-lock.yaml <!-- 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!} <!-- /greptile_comment -->