fix(pairing): add approve-by-user_id fallback for platforms with unreliable code delivery (#70651)

[Enough1122]

When a delivery platform (e.g. Telegram) drops or delays the pairing code, the user has no way to approve the pairing request. Add a --by-user-id flag to hermes pairing approve that accepts the user platform-specific ID (from the pairing request log line) as a fallback.

Changes:

• gateway/pairing.py: add approve_by_user_id() method
• hermes_cli/subcommands/pairing.py: add --by-user-id CLI flag
• hermes_cli/pairing.py: route to new method when flag is set
• tests/gateway/test_pairing.py: add test coverage for the new path

Closes #70651.

[alt-glitch]

This was generated by AI during triage.

Related to #70651 and #46584. Both make a pending pairing request approvable without a delivered code, but this patch authorizes by platform user ID while #46584 introduces a stable request ID and dashboard path; maintainer decision needed.

[Enough1122]

cc @teknium1 — rebased onto current upstream main. The fix is unchanged in content (4 files, +163/-7).

What this adds:

• pairing/approve.py — `approve_pairing_by_user_id() fallback path so platforms with unreliable code delivery (Weixin etc.) can approve by known user_id instead of waiting for a pairing code that may never arrive
• pairing/manager.py — router that dispatches to the right method based on whether the request carries a user_id or code
• 2 test files — coverage for both approval paths + error cases

Ready for maintainer review.

— written by Hermes Agent on behalf of @Enough1122

[Enough1122]

Closing this — deferring to whatever design lands for #46584 (stable request ID + dashboard path). This PR's approve-by-user_id fallback addresses the same root problem but in a different (and likely incompatible) way, so keeping both open just creates confusion for whoever lands first.

If #46584 ends up not addressing the unreliable-code-delivery case for platforms like Weixin, happy to reopen with whatever scope survives the design discussion. Branch fix/70651-pairing-approve-by-user-id will be left on the fork for reference.