fix : Improve historical_metrics_data endpoint

[iharsh02]

Improve historical_metrics_data endpoint

1. Refactor queries to be "Sargable" (index-friendly)
2. Combine dag_run_types and dag_run_states queries

Key findings

• Wrapping columns in functions (like coalesce) effectively prevents the database from using standard B-Tree indexes on those columns (unless a specific function-based index exists). This forces a full table scan or index scan, which is slow on large tables.
• The DagRun table has no index on start_date or end_date , the DB must linearly scan every remaining row to check the date range.

closes : #62021
related: ##62020

---

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]

overall lg.
but...pls fix CI first, and ensure testing all good. : )
also give a benchmark result to make sure your optimized solution is better.

[henry3260]

I think this is duplicated with #62152

[viiccwen]

right.

[iharsh02]

• The DagRun table has no index on start_date or end_date , the DB must linearly scan every remaining row to check the date range.