Add MR Approved Trigger Configuration UI for Flows and Agents
## Add MR Approved Trigger Configuration UI for Flows and Agents
### Summary
Introduce a trigger configuration interface that allows users to set up an **MR Approved** trigger for their flows and agents — enabling automation to fire when a merge request is approved — directly from the GitLab UI.
---
### Design
Figma: https://www.figma.com/design/8dIIoI6h78WTjXbUTp0yOI/Agent-Workflow-Catalog?node-id=13039-101954&t=ClpBtTt9a7co3cbp-1
---
### Background
The backend implementation for the `merge_request_approval_operation` audit event (filtered on `action: approve`) is tracked in [#592456](https://gitlab.com/gitlab-org/gitlab/-/work_items/592456). Once users can select **MR Approved** as a trigger type for flows and agents, they need a corresponding UI to configure and manage this trigger.
This issue covers the frontend work to surface the MR Approved trigger in the **New Trigger** form under `Automate > Triggers`.
---
### Problem
Without a configuration UI for the MR Approved trigger, users cannot:
* Set up automation that fires when a merge request is approved (e.g., to run a pre-merge checklist agent)
* Configure a flow to draft release notes when an MR is approved
* View or manage existing MR Approved triggers from the GitLab UI
---
### Proposed Solution
Extend the **New Trigger** form under `Automate > Triggers` to support **MR Approved** as a selectable trigger type. The UI should:
* Display **MR Approved** as an option in the trigger type selector
* Show relevant context or help text explaining when the trigger fires (on `merge_request_approval_operation` with `action: approve`)
* Persist and display the trigger correctly when viewing an existing trigger configuration
---
### Acceptance Criteria
- [ ] **MR Approved** is available as a trigger type option in the New Trigger form
- [ ] Selecting **MR Approved** shows appropriate configuration UI and help text
- [ ] The trigger is persisted and displayed correctly when viewing an existing trigger
- [ ] The trigger only fires on MR approval events (not on approval removal)
- [ ] UI matches the design spec
issue