#19241: docs(telegram): fix 5 discrepancies between docs and config schema

Fixes discrepancies identified in #19222. ## Changes Cross-referenced `docs/channels/telegram.md` against the config schema and source types (`src/config/types.telegram.ts`) and found 5 missing fields in the config reference section: ### Added - `channels.telegram.actions.editMessage` — was present in the accordion and the high-signal summary but missing from the per-field reference list - `channels.telegram.groups.<id>.tools` — per-group tool policy override (`allow`, `alsoAllow`, `deny`) - `channels.telegram.groups.<id>.toolsBySender.<senderId>` — per-sender tool policy override within a group - `channels.telegram.blockStreaming` — boolean to suppress live stream previews - `channels.telegram.markdown.tables` — table rendering mode (`off | bullets | code`) - `channels.telegram.accounts.<account>.name` — optional display name for the account ## Verification All added fields confirmed present in `src/config/types.telegram.ts` and `src/config/types.base.ts`. <!-- greptile_comment --> <h3>Greptile Summary</h3> Added 6 missing Telegram configuration fields to the documentation reference section. All fields are verified to exist in `src/config/types.telegram.ts` and `src/config/types.base.ts`: - `channels.telegram.actions.editMessage` — tool action gate for message editing (already documented in Actions section but missing from config reference) - `channels.telegram.groups.<id>.tools` — per-group tool policy override - `channels.telegram.groups.<id>.toolsBySender.<senderId>` — per-sender tool policy override within groups - `channels.telegram.blockStreaming` — boolean flag to suppress stream previews - `channels.telegram.markdown.tables` — table rendering mode configuration - `channels.telegram.accounts.<account>.name` — optional account display name The documentation additions match the schema types exactly and maintain consistency with existing documentation patterns. <h3>Confidence Score: 5/5</h3> - This PR is safe to merge with no concerns - it only adds missing documentation entries. - Documentation-only change that accurately reflects the existing codebase. All added fields are verified to exist in the source schema files with matching types and descriptions. No code changes, no runtime impact, and follows existing documentation patterns. - No files require special attention _{Last reviewed commit: f84fa29} <!-- greptile_other_comments_section --> _{(2/5) Greptile learns from your feedback when you react with thumbs up/down!} <!-- /greptile_comment -->