fix(qqbot): cap stale resume retries and fallback to identify

[chongru1988]

Summary

• Limit consecutive QQ gateway Resume attempts to avoid endless reconnect loops on stale sessions.
• Add a fallback path that clears stale session state and sends Identify after the resume cap is reached.
• Reset resume-attempt state on recovery/error paths (READY, RESUMED, session-invalid, and resume-send failure).

Why

Some stale-session reconnect flows can repeatedly attempt Resume without making progress. This change makes recovery deterministic by forcing a clean Identify handshake after bounded retries.

Changes

• gateway/platforms/qqbot/constants.py
  • add MAX_RESUME_ATTEMPTS
• gateway/platforms/qqbot/adapter.py
  • track resume attempts
  • enforce cap in Hello auth mode selection
  • fallback to Identify when cap is reached
  • reset counter on success/error recovery paths
• tests/gateway/test_qqbot.py
  • add regression tests for Hello auth mode selection

Test Plan

• python -m pytest tests/gateway/test_qqbot.py -k "HelloAuthModeSelection or ReadyHandling" -q -n 4
• Result: 4 passed

Linked Issue

• Closes fix(qqbot): cap Resume retries and fall back to Identify on stale session #22384

[alt-glitch]

Competing fix — see #22384 which addresses the same QQBot Resume death-loop (#22179). Also related to #17990.

[teknium1]

Thanks for targeting the stale QQ Resume path. The premise remains present on current main: the Hello handler still chooses Resume solely from _session_id / _last_seq (gateway/platforms/qqbot/adapter.py:830-834).

Problems

• The cap cannot recover the PR's stated “immediately closes” case. The PR sends Resume for attempts 1–3 and selects Identify only on Hello 4, but current main exits after the third quick disconnect (gateway/platforms/qqbot/adapter.py:515-534). That prevents the fallback from running.
• The new tests seed _resume_attempts at the cap, so they do not exercise the current listener's immediate-close / quick-disconnect path.

Suggested changes

• Reconcile the Resume cap with the quick-disconnect cutoff so stale sessions reach Identify before listener termination, while retaining the current 4009-resumable behavior at gateway/platforms/qqbot/adapter.py:600-627.
• Add an async regression covering consecutive immediate closes through the actual reconnect loop.

Automated hermes-sweeper review.

[teknium1]

This fallback is only entered on the fourth Hello: the first three Hellos increment and send Resume. For the stated immediate-close failure, current main exits after its third quick disconnect (_listen_loop, gateway/platforms/qqbot/adapter.py:515-534), so this branch is never reached. Please coordinate the threshold with that guard and add a reconnect-loop regression.