feat(feishu): render markdown tables as native card tables

[kreshan1997-alt]

Problem

Feishu post-type messages do not render markdown tables. When the agent responds with table content, it appears blank or as raw pipe-separated text. Current workaround forces plain text for any content containing a table, losing all formatting.

Solution

Detect markdown tables in outbound messages and send them as interactive cards with a native table element (Feishu card schema 2.0), while preserving surrounding markdown text.

Changes

1. _parse_md_table_content() — Parse markdown table structure and split surrounding text
2. _build_table_card_payload() — Build Feishu 2.0 card with table element
3. _build_outbound_payload() — Route tables as interactive msg_type
4. Fallback in send() — Degrade interactive cards to plain text on API rejection

Testing

Verified on live Feishu bot with various table sizes and mixed content. Fallback confirmed on API rejection.

[alt-glitch]

This was generated by AI during triage.

Duplicate of #12114 — same native Feishu Card 2.0 table-element rendering for markdown tables, the earliest-open PR in a heavily saturated cluster (#40445, #38453, #31038, #46727, #26429). Tracking the canonical there.

[teknium1]

Thanks for addressing a real Feishu rendering limitation: current main deliberately falls back to plain text for detected markdown tables at plugins/platforms/feishu/adapter.py:4524-4530.

Problems

• The new parser uses one _MARKDOWN_TABLE_RE.search() and places all later content in a markdown element. A second table in the same response would remain markdown, despite the current adapter documenting that this renderer does not support tables.
• edit_message() also uses _build_outbound_payload() at plugins/platforms/feishu/adapter.py:1958, but its fallback remains msg_type == "post" at line 1963. The submitted fallback change covers send() only.
• The diff changes no tests, leaving table segmentation and both interactive fallback paths unprotected.

Suggested changes

• Segment all recognized tables in order and cover multi-table content.
• Apply a consistent interactive fallback to both send and edit paths, then add regression tests under tests/gateway/.

Automated hermes-sweeper review.