fix(ui): prevent duplicate TI summary stream refreshes after mutations

[durgaprasadml]

Summary

Closes#67884

This fixes a UI freeze regression introduced after #67212 where Task Instance mutation actions (Mark success/failed, etc.) triggered multiple overlapping TI summary stream refreshes and excessive React state updates.

Previously:

• multiple query invalidations could trigger multiple stream restarts
• overlapping NDJSON streams emitted duplicate updates
• each streamed line caused an individual React state update
• expensive grid/task-instance rendering amplified the render pressure
• the UI became temporarily unresponsive for several seconds after mutation actions

This update introduces deterministic refresh coalescing, active stream deduplication, and NDJSON state batching to significantly reduce render churn while preserving query freshness and the stale badge fix introduced in #67212.

---

Root Cause

The cache subscriber added in #67212 relied on a fragile timing-based debounce using setTimeout(..., 0).

Under mutation-heavy invalidation flows:

• multiple query invalidations emitted separate cache notifications
• refresh scheduling could execute multiple times
• multiple TI summary streams became active simultaneously
• every NDJSON line triggered a separate setSummariesByRunId update

This resulted in dozens of rapid re-renders on already expensive UI surfaces.

---

Changes

Deterministic Refresh Coalescing

• replaced the fragile timeout-based refresh scheduling
• introduced frame-based refresh coalescing using requestAnimationFrame
• collapses multiple invalidation notifications into a single refresh cycle

Active Stream Deduplication

• stale streams are now aborted correctly
• aborted streams immediately stop processing NDJSON updates
• prevents obsolete stream instances from updating React state

NDJSON State Batching

• buffered streamed summaries per read chunk
• applied updates in a single batched state update instead of once-per-line
• significantly reduced render frequency and Map cloning overhead

---

Tests Added

Added comprehensive tests covering:

• multiple invalidations collapsing into one refresh
• stale stream abort handling
• NDJSON batching behavior
• stable mount behavior
• prevention of duplicate refresh scheduling

---

Verification

Validated with:
bash npx vitest run src/queries/useGridTISummaries.test.tsx pnpm lint

No lint or type errors remain.

[bbovenzi]

Good catch!

[choo121600]

Nice! It looks like the static check is failing.
The document below may help you resolve the issue.
https://github.com/apache/airflow/blob/main/contributing-docs/08_static_code_checks.rst

[boring-cyborg]

Awesome work, congrats on your first merged pull request! You are invited to check our Issue Tracker for additional contributions.

[github-actions]

Backport failed to create: v3-2-test. View the failure log Run details

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-2-test

You can attempt to backport this manually by running:

cherry_picker 2e5af2a v3-2-test

This should apply the commit to the v3-2-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

If you don't have cherry-picker installed, see the installation guide.