[Feat] Route manager updates to every communication channel

[roomote-community]

Created by Roomote. Follow up by mentioning @roomote, in the web UI, or in Discord.

What changed

• lets admins choose Slack, Discord, Microsoft Teams, or Telegram for the shared Automation output destination
• persists Teams and Telegram manager destinations with additive schema fields and resolves them through the existing provider-neutral automation routing
• routes platform issue alerts and custom automation defaults through the selected manager destination
• preserves newly configured destinations when older settings clients omit provider fields
• requires active Telegram bot credentials before accepting a Telegram manager destination
• updates in-product guidance and public automation docs to use provider-neutral language

Why this change was made

Manager-facing automation updates were still configured around Slack and Discord even though Roomote supports additional communication providers. This starts the migration to one shared destination model across every supported communications surface.

Impact

Admins can route manager asks, summaries, suggestions, and alerts to their connected Teams primary conversation or Telegram primary chat without changing existing Slack or Discord behavior. Telegram destinations are rejected when bot runtime credentials are unavailable, preventing reports from being routed to an unusable destination. Existing deployments remain compatible through an additive migration and omission-safe update handling.

[roomote-community]

No new code issues found. See task

• apps/web/src/trpc/commands/automations/settings-update.ts:399-409 Saving a Telegram manager destination validates only TELEGRAM_PRIMARY_CHAT_ID, not Telegram runtime credentials. A stale chat ID can therefore replace a working output, then every manager report resolves to Telegram while no adapter exists and delivery is skipped. Require an active Telegram adapter/credentials before accepting the destination.

_{Reviewed 74eae2e}

[roomote-community]

Fixed the Telegram manager-destination validation in 74eae2e. Saves now require an active Telegram communication adapter after the primary chat ID matches, and regression coverage confirms missing bot credentials leave the destination unset.