[github-actions]

• UI: Stop Recent Configurations flashing on the trigger form

The section decided to hide itself only once its runs had arrived, so every
time the trigger form opened it first drew an empty, disabled select and then
either filled it or removed it. The query does not start until the modal
opens, which reports as pending rather than loading, so neither flag on its
own tells you the runs are in hand.

Co-Authored-By: Claude noreply@anthropic.com

• UI: Lay out Recent Configurations like the rest of the trigger form

Every other row in the form names itself in a column down the left and puts
its control to the right. This one announced itself in small type above a
control that ran the full width, so the eye had to change track in the middle
of the form.

Co-Authored-By: Claude noreply@anthropic.com

• UI: Offer recent configurations when they come from cache

Runs stay fresh for five minutes, so reopening the trigger form inside that
window serves them from cache without fetching. Asking the query whether it
had fetched since mounting read that as "not ready" and hid configurations
that were already in hand.

Nothing needs asking. The options are built from the runs alone, so they are
empty both before the runs arrive and when none of them carried a config, and
in either case there is nothing to show.

Co-Authored-By: Claude noreply@anthropic.com

---

(cherry picked from commit 212fe09)

Co-authored-by: Brent Bovenzi brent@astronomer.io
Co-authored-by: Claude noreply@anthropic.com