fix(cron): retain host-verified requesters across channels (#201159)

Problem: an automation created from a channel chat must remember who created it and on which account, so each run can check that owner. #201008 fixed this for Telegram with a Telegram-specific branch next to an older Discord-specific path; other channels (Slack, WhatsApp, ...) still saved no creator, and core code branched on channel names.

Fix: the creator comes from the owner identity that the shared channel ingress already verified (`channelPrincipal`, added in #201008), for every channel. The `discord`/`telegram` branches and the configured-owner fallback are removed. Missing, mismatched, revoked or unverified owner authority still cannot establish ownership.

User impact: automations created by a verified channel owner on any channel keep their creator and account, so their runs pass the account check. A sender recognized as owner only by config/alias matching, without a verified ingress identity, no longer creates automations as owner.

Proof: Slack host-ingress capture (default and work accounts) and persisted origin/requester integration fail on base and pass on head; existing Telegram and Discord cases pass. Builds on Vincent Koc's #201008.

Co-authored-by: Ayaan Zaidi <hi@obviy.us>