Service GCC - Marking a triggered DagRun as failed does not appear to work as expected.

[stubs]

Describe the bug

While familiarizing myself with the TUI I triggered a small dag for a manual dagRun. To kick the tires on marking a dagRun with some state, I chose to mark the triggered dagRun as "failed". I noticed that the TUI immediately reflected the stopped the dagRun, but it was still green. Upon checking my Cloud Composer GUI I saw that the manual triggered DagRun was also marked as having a status of "success".

In the Cloud Composer GUI, after updating the status to "failed" I did see the nice red indicator in the flowrs TUI for that manually triggered dagRun.

Not sure if this only occurs with the failed status or if it also occurs with queued as well.

To Reproduce

1. config the cloud composer service
2. ensure you have some airflow dag that you can test with (e.g. maybe some no op dag that just uses a bunch of empty operators, etc.)
3. in flowrs:
   • trigger that dag with t.
   • nav to the newly triggered dagRun, and press m to begin the process to mark the dag run as having a certain state. Choose failed.

Expected behavior

When a dagRun is marked as failed with flowrs, the dagRun should be marked as failed in Airflow.

Desktop (please complete the following information):

• OS:

ProductName:            macOS
ProductVersion:         26.3
BuildVersion:           25D125

• Version: flowrs 0.12.2