Implement and integrate configurable event triggers with the Events Platform
### Summary
This issue covers the event triggering side of the [Event Platform project](https://gitlab.com/groups/gitlab-org/-/work_items/21338), which enables an event-driven GitLab Duo Flow automation that responds to both internal GitLab events and external system events.
While the platform infrastructure is being handled separately ([Phase 1](https://gitlab.com/groups/gitlab-org/-/work_items/21345), [Phase 2](https://gitlab.com/groups/gitlab-org/-/work_items/21346)), this work focuses on identifying where events are triggered in the codebase, calling the Event Service when trigger conditions are met, and making triggers configurable through the UI.
### Background
The Event Platform consists of two parts:
1. **Platform:** the infrastructure and event service (tracked separately)
2. **Triggers:** identifying and implementing the points in the codebase where events are fired (**this issue**)
#### Requirement
1. When a user action meets a trigger condition (e.g. creating an issue, assigning an issue), the system needs to call the Event Platform Service, which then publishes the event.
2. The triggers must be configurable via the UI
3. The available triggers must be dependent on the selected flow.
#### Goals
- Extend the existing event trigger types to support the Event Platform
- Identify where in the codebase trigger conditions are met and wire them up to call the Event Service
- Ensure triggers are configurable and flow-dependent
#### Dependencies
- Depends on a working Events Platform
- Trigger implementation cannot be fully integrated or tested e2e until the platform infrastructure and Event Service are operational
#### Definition of Done
- [ ] Flow trigger architecture documented and shared with team
- [ ] Priority list of triggers agreed upon
- [ ] Trigger conditions identified in the codebase for each prioritised trigger
- [ ] Event Service called when trigger conditions are met
- [ ] Triggers are configurable via the UI
- [ ] Available triggers are flow-dependent
#### References
- Parent epic: https://gitlab.com/groups/gitlab-org/-/work_items/21338
- Events Platform POC: https://gitlab.com/gitlab-org/cluster-integration/gitlab-agent/-/merge_requests/3350
- POC: Duo Code Review using GitLab Events Platform: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/227702
- Add Flow Triggers and Event Design Doc: https://gitlab.com/gitlab-com/content-sites/handbook/-/merge_requests/18106
- Event Store docs: https://docs.gitlab.com/development/event_store/
- List of GitLab Duo Triggers and Agents: [internal docs](https://docs.google.com/spreadsheets/d/1bL6q1h8N1bqWuRIcyfvBTovYVSEK0oQmfsLNnOlfMU0/edit?gid=2114036493#gid=2114036493)
- Implement MR Approved trigger: https://gitlab.com/gitlab-org/gitlab/-/work_items/592456
- Q1 triggers discussion: https://gitlab.com/groups/gitlab-org/-/work_items/20465#note_3148692053
issue