fix(feishu): infer receive_id_type from chat_id prefix

[dalianmao000]

Summary

• Infer receive_id_type from chat_id prefix to support all Feishu ID types:
  • ou_ prefix → open_id
  • on_ prefix → union_id
  • default → chat_id
• Previously hardcoded receive_id_type="chat_id" which caused Feishu API error [230001] invalid receive_id for open_id targets

Fixes

Fixes #7685

Test plan

• Create cron job with deliver: "feishu:ou_xxxxx" and verify delivery succeeds
• Verify chat_id (oc_) and union_id (on_) targets still work

🤖 Generated with Claude Code

[alt-glitch]

Likely duplicate of #7694 — same fix (infer receive_id_type from chat_id prefix in Feishu adapter). Both fix #7685. Also overlaps with #10040.

[teknium1]

Thanks for identifying the Feishu recipient-type gap. The union-ID portion remains valid on current main.

Problems

• The PR targets gateway/platforms/feishu.py, but commit 5600105478ffde29d7566b45421b100eaa29c4ef moved the live adapter to plugins/platforms/feishu/adapter.py; the submitted patch cannot apply.
• Current main already maps ou_ to open_id at plugins/platforms/feishu/adapter.py:4641-4642. However, on_ still falls through from the chat_id default at :4637 to request construction at :4650.
• The PR contains no regression test. tests/gateway/test_stream_consumer_thread_routing.py:176-280 already exercises this plugin adapter path.

Suggested changes

• Salvage only an on_ → union_id branch into plugins/platforms/feishu/adapter.py, retaining the existing feishu_user_id:, ou_, and thread handling.
• Add a plugin-adapter regression test for on_ delivery using the existing _run_blocking test pattern.

Automated hermes-sweeper review.