fix(feishu): prevent [99992402] field validation failed in thread replies

[leowzz]

Summary

• add feishu.reply_in_thread so replies to top-level Feishu/Lark messages can start a topic
• preserve the existing default (false) for backward compatibility while keeping replies inside existing topics
• fix an issue where jobs created inside a Feishu thread could deliver to the parent chat or fail delivery, causing users to miss the job response in the originating thread
• avoid unsupported receive_id_type=thread_id create requests, which Feishu rejects with 99992402 field validation failed
• preserve the triggering Feishu message ID when a cron job is created inside a topic, then use it as reply_to_message_id for both live and standalone delivery
• only fall back to the parent chat when a topic delivery genuinely no longer has a valid reply anchor
• avoid treating Feishu SDK response objects as dictionaries during live-delivery confirmation
• document the setting in the English and Chinese Feishu guides

Testing

• scripts/run_tests.sh tests/cron/test_scheduler.py tests/tools/test_cronjob_tools.py tests/tools/test_send_message_tool.py tests/gateway/test_feishu.py tests/gateway/test_stream_consumer_thread_routing.py tests/gateway/test_run_progress_topics.py -q --tb=short
• 707 tests passed
• git diff --check

[leowzz]

This mixed feature/fix PR has been split into two focused PRs based on the latest main:

• Feature (feishu.reply_in_thread): feat(feishu): add configurable reply-in-thread behavior #65519
• Fix ([99992402] and thread-scoped job delivery): fix(feishu): prevent [99992402] in thread and job delivery #65520

Closing this superseded PR to keep review scope and commit history focused.