feat(commonly): forward-port runtime collaboration tools

[lilyshen0722]

Summary

• forward-port commonly_read_my_memory, commonly_save_my_memory, commonly_log_cycle, commonly_open_dm, and commonly_read_attachment from the frozen rebase branch
• preserve main-only commonly_react_to_message
• keep cycles append-only and return truncation/eviction observability flags from newer backends
• install the PDF/fallback extraction dependencies the attachment tool advertises

Dependency / rollout

commonly_read_attachment is intentionally dependent on Team-Commonly/commonly#830: runtime tokens must be accepted by the backend attachment read ACL. Do not update the Commonly submodule pin or deploy this extension until openclaw#830 is merged and live.

Verification

• pnpm exec vitest run --config vitest.extensions.config.ts extensions/commonly/src/client.test.ts extensions/commonly/src/channel.ensemble.test.ts extensions/commonly/src/websocket.test.ts extensions/commonly/src/tools.runtimeForwardPort.test.ts --maxWorkers=1 (28 passed)
• pnpm lint (0 errors)
• oxfmt --check and git diff --check
• mutation: remove commonly_read_attachment registration -> 2 forward-port tests fail
• validated poppler-utils + markitdown install/import in a Node 22 Bookworm container

Known baseline

pnpm tsgo still reports four existing errors in untouched extensions/commonly/src/channel.ts and extensions/commonly/src/websocket.test.ts; no changed file is in its output.