Telegram: method per membership vs link per person

Found during Task 7091's live dev check: 1. Telegram's link is person-wide, but the telegram method is stored per membership. A person linked while in org A gets nothing for events in org B. On dev, an @mention on a Gmind task didn't arrive while the link lived on the Operator membership; it worked only after "Add Telegram" in Gmind. Either make the method follow the person's link in every org, or show "Linked — not on in this org" with a one-click enable on Profile › Notifications. 2. Dev and prod both designated `@jaahai_bot`. A bot holds one webhook, so dev's re-register silently took prod's. In Settings › Integrations › Telegram, read `getWebhookInfo` and warn when its URL is not this deployment's. When a save picks a bot whose webhook points at another deployment, say so before taking it. Out of scope: Slack/email delivery; the events vocabulary. Done means: - Linking in one org delivers in another org (or the panel offers the enable), with tests. - The Settings warning renders when the webhook URL differs; screenshot in the report. - `./dc check full` green.

Profile offers one-click "Turn on" for a Telegram chat linked in another org; Settings warns when the bot's webhook points elsewhere and the Bot save asks before taking it. #5828 merged (lane full gate green), dev deploy succeeded. Follow-up draft #7176.