Triggers list UI paper cuts

What does this MR do and why?

Makes a number of small UI changes to improve the general usability and comprehension of triggers. Trigger CRUD will be addressed in a follow up.

• Clarify trigger purpose in header
• Shift to always show fluid layout so the table has room to expand
• Increase width of events column since this will grow with new events
• Rename "Event type" to Event
• Refactor "Config Path" to "Target", show flows and agents as well as config path
• Force all field values to be right-aligned in reflowed stacked view for consistency
• Updated empty state illustration and copy to not reference pipelines

References

Screenshots or screen recordings

Before	After	Context
		With records
		No triggers, has flows/agents/config files

How to set up and validate locally

1. Setup GDK with AI features enabled
2. Navigate to a top level group /-/automate/triggers
3. To test empty state, find a group/project with no triggers setup

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.