UI: Optimize grid view refresh pressure on the API

[viiccwen]

Summary

This PR adjust how the Grid view refreshes task summaries by slowing down refreshing pending tasks.

• closes UI - Improve refresh rate strategy of the Grid view #62033
• related API - UI Optimization #62020

Detailed

1. adds isSelected parameter in useGridTiSummaries hook.
2. only keep the selected DAG run on the default useAutoRefresh interval. (3s)
3. slow down non-selected DAG run by a fixed multiplier. (currently 5x -> 15s, we can discuss in the comments : D)

Benchmark results

Visible DAG runs	Before (requests / 60s)	After (requests / 60s)	Reduction
5	100	36	64%
10	200	56	72%
25	500	116	76.8%
50	1000	216	78.4%

This result only calculates ideally, not in realistic situation. (bcz we need to consider about network etc.)

• The currently selected DAG run still refreshes at the original auto-refresh interval, so the behavior as before.
• Non-selected runs refresh less frequently, but still often enough to serve as an overview. (IMO)

No API contract changes are introduced; the change is limited to the Grid view’s client-side polling strategy.

---

Was generative AI tooling used to co-author this PR?

• Yes (please specify the tool below)

---

• Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
• For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
• When adding dependency, check compliance with the ASF 3rd Party License Policy.
• For significant user-facing changes create newsfragment: {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

[viiccwen]

cc @pierrejeambrun 🙌
IMO, I consider we can use 5x to slow down the non-selected pending DAG runs (3s -> 15s). WDYT?
and maybe we should let the multiplier become a config variable, not just a magic number. : )?

[pierrejeambrun]

LGMT thanks

[github-actions]

Backport successfully created: v3-1-test

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status	Branch	Result
✅	v3-1-test

[viiccwen]

@pierrejeambrun oh, thx for reviewing. ><