[v3-1-test] Manually Backport fix(ui): handle pools with unlimited (-1) slots in UI components (#62831)

[choo121600]

Backport of #62831

• fix(ui): handle pools with unlimited (-1) slots in UI components

When a pool has slots set to -1 (unlimited), the UI now properly handles this case instead of showing broken bars or negative values.

Changes:

• PoolBar: render infinity symbol and proportional bar for unlimited pools
• PoolBarCard: display ∞ instead of -1 in pool header
• PoolSummary: correctly aggregate slots when any pool is unlimited
• PoolForm: set min to -1 and add helper text explaining the convention

Closes: #61115

• fix(ui): simplify PoolBar unlimited slots computation per review

• fix(ui): rename short identifier in PoolBar filter/reduce

• fix(ui): resolve linting and typing errors caught by prek

• Fix indentation in PoolBar.tsx map callback (formatting)
• Fix JSX line break in PoolBarCard.tsx (formatting)
• Widen slotType cast to TaskInstanceState | "open" since open_slots produces "open" which is not a TaskInstanceState
• Add explicit cast for StateIcon prop where "open" is already filtered out by infoSlots

---

---

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, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

[pierrejeambrun]

Thanks