Add autorefresh to Task Instance and Dag Run pages

[bbovenzi]

Add auto refresh to the new UI, starting with the task instance and dag run pages

What should refresh:

• Task Instance: Header, details, tries and logs
• Dag Run: Header, details and the list of task instances

---

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in newsfragments.

[tirkarthi]

@bbovenzi Will there be a toggle to disable auto refresh that persists across views in 3.0 like legacy UI?

[pierrejeambrun]

Code looks good. Tested and working as expected. Nice.

[pierrejeambrun]

@bbovenzi Will there be a toggle to disable auto refresh that persists across views in 3.0 like legacy UI?

Is there a particular use case ? Otherwise IMO that just feels old and outdated without auto-refresh, I would be for completely removing that toggle in airflow 3 UI.

[bbovenzi]

Yes, I was leaning towards removing the toggle, being smarter with when its used, and if someone doesn't want any autorefresh then they don't need to specify it in their config.

[bbovenzi]

Gonna merge but we can keep talking about a pause autorefresh button

[tirkarthi]

The old UI used to have auto refresh only on when there is focus on running dagrun in the grid. I remember sometimes there was a trigger in another tab and I used to manually do the toggle. There could be just a manual refresh button in the header instead of a toggle too. I don't have any strong opinion on this. autorefresh toggle also means more code and maintenance to persist the state and if I remember correctly it used to be a provider to the app object. There will be user feedback during testing to see if there is more demand for the component.

Thanks @bbovenzi .

[bbovenzi]

I think both of those use cases can be covered with us being smarter on when we invalidate queries and which queries need a refetchInterval function