fix(feishu): ignore thread_id in DM quoted replies to prevent isolated sessions

[liuhao1024]

What does this PR do?

Fixes a bug where quoted replies (引用回复) in Feishu DMs create isolated sessions, causing the agent to lose all conversation context. The Lark SDK populates thread_id for DM quoted replies, but Feishu DMs don't support real threads — the field is erroneously used to build a different session key.

Related Issue

Fixes #44028

Type of Change

• 🐛 Bug fix (non-breaking change that fixes an issue)

Changes Made

• gateway/platforms/feishu.py: Clear thread_id when chat_type == "p2p" so DM quoted replies stay in the normal DM session. Group thread behavior is preserved.
• tests/gateway/test_feishu.py: Added two regression tests — DM quoted reply strips thread_id, group reply preserves it.

How to Test

1. Configure a Feishu bot with DM access
2. Start a conversation with the bot (normal messages work fine)
3. Send a quoted reply to one of the bot's messages
4. Before fix: agent loses context (new empty session created)
5. After fix: agent continues in the same session with full context

pytest tests/gateway/test_feishu.py::TestFeishuProcessInboundMessage::test_dm_quoted_reply_does_not_create_thread_session tests/gateway/test_feishu.py::TestFeishuProcessInboundMessage::test_group_quoted_reply_preserves_thread_id -v

Checklist

Code

• I've read the Contributing Guide
• My commit messages follow Conventional Commits (fix(scope):, feat(scope):, etc.)
• I searched for existing PRs to make sure this isn't a duplicate
• My PR contains only changes related to this fix/feature (no unrelated commits)
• I've run pytest tests/ -q and all tests pass
• I've added tests for my changes (required for bug fixes, strongly encouraged for features)
• I've tested on my platform: macOS

Documentation & Housekeeping

• I've updated relevant documentation (README, docs/, docstrings) — or N/A
• I've updated cli-config.yaml.example if I added/changed config keys — or N/A
• I've updated CONTRIBUTING.md or AGENTS.md if I changed architecture or workflows — or N/A
• I've considered cross-platform impact (Windows, macOS) per the compatibility guide — or N/A
• I've updated tool descriptions/schemas if I changed tool behavior — or N/A

Code Intelligence

• Analyzed: FeishuAdapter._process_inbound_message() (callers: Lark SDK event handler, flows: 1)
• Blast radius: LOW — only affects Feishu DM inbound message processing
• Related patterns: Session key builder uses thread_id for group threads; DMs should not use it

[alt-glitch]

Duplicate of #36233 — same root cause and fix (clear thread_id for chat_type=='p2p' so Feishu DM quoted replies stay in the main DM session). #36233 is the earliest open canonical PR; #44083/#44058 are closed twins.

[liuhao1024]

Thanks for the flag @alt-glitch. Confirmed — #36233 covers the same root cause with a more comprehensive approach (+342/-13 across 4 files vs this PR's +55). Closing in favor of #36233.