Let Developers view the project Automations page

What does this MR do and why?

Today only Maintainers can open the project Automations (Triggers) page, because the page, the sidebar item and the GraphQL resolver check manage_ai_flow_triggers. Developers already have read_ai_flow_triggers, and AiFlowTriggerType already authorizes on it. This merge request changes those three checks to read_ai_flow_triggers, so Developers can view automations, their details and their runs. Run counts and sessions stay scoped to the sessions the user can read.

Creating, editing, deleting and turning automations on or off still need manage_ai_flow_triggers, which the mutations already enforce. The frontend now uses the manageAiFlowTriggers ability that the controller already pushes: it hides the new buttons and row actions, disables the active toggle, drops the create prompt from the empty state, and redirects the new and edit routes to the index. The change applies to both the old Triggers page and the new Automations page. The admin_ai_catalog_item_consumer custom ability also gets read_ai_flow_triggers, so its users keep access to the page.

https://gitlab.com/groups/gitlab-org/-/work_items/23940

References

Screenshots or screen recordings

Before	After

How to set up and validate locally

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.