test: add event-trigger routine e2e coverage

[henrypark133]

Summary

• add E2E coverage for Telegram-scoped event routines
• add E2E coverage for event routines without an event_channel filter
• verify that matching incoming Telegram messages create routine runs and broadcast routine output

Test Plan

• cargo test --test e2e_advanced_traces routine_event_trigger --features libsql

[gemini-code-assist]

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

[Copilot]

Pull request overview

This PR adds E2E test coverage for event-trigger routines, specifically testing that Telegram-scoped and channel-agnostic event routines correctly fire when matching incoming messages are received.

Changes:

• Two new LLM trace fixtures for Telegram-scoped and any-channel event routines
• A shared wait_for_routine_run polling helper and two new test functions in e2e_advanced_traces.rs

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File	Description
tests/fixtures/llm_traces/advanced/routine_event_telegram.json	LLM trace fixture for a Telegram-scoped event routine creation and trigger
tests/fixtures/llm_traces/advanced/routine_event_any_channel.json	LLM trace fixture for a channel-agnostic event routine creation and trigger
tests/e2e_advanced_traces.rs	Adds wait_for_routine_run helper and two new E2E tests verifying event routine triggers

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[zmanian]

Good test coverage for event-trigger routines. The channel-scoped and any-channel variants cover the important edge cases. Clean fixture setup. LGTM.