[Feat] Track automation activation events

[roomote-roomote]

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

What changed

• Emit anonymous instance-level activation events for every built-in automation that transitions between enabled and disabled states, including starter automations enabled as a manager-channel side effect.
• Emit activation events when custom automations are created or deleted through either the web settings flow or MCP API.
• Restrict event properties to canonical built-in automation identifiers and allowlisted destination providers.

Why this change was made

Automation activation is an important product milestone, but it was not represented in the activation telemetry funnel. These events add that signal without collecting custom automation names, prompts, channel details, user data, or other customer content.

Impact

There is no user-facing behavior change. Anonymous analytics can now measure direct and automatic built-in automation enablement plus custom automation lifecycle activity with privacy-safe classifications only.

[roomote-community]

No code issues found. See task

• apps/web/src/trpc/commands/automations/settings-update.ts:1385 — Capture all built-in state transitions, not only savingAutomation. Resolved in 444dcb8: settings saves compare every built-in automation state, and Slack manager-channel onboarding emits the same starter-automation activation events after it succeeds.

_{Reviewed 444dcb8}

[roomote-roomote]

Fixed the activation-tracking gap in 444dcb8. Settings saves now compare every built-in automation state, so manager-channel cascades emit all three starter activation events. Slack manager-channel onboarding now emits the same events after the onboarding flow succeeds.