[ydsakshi]

Description

Addresses one more filter requirement of #53049

Adds duration From/To on the DAGs backfill tab. so that backfills can be filtered by how long they ran.

In-progress backfills are excluded.

Evidence Screenshots

Scenario	Evidence	Assert
Base Case		2 backfills
-	-	-
Duration >= 18 sec		1 backfill
-	-	-
Duration <= 29 sec		2 backfills
-	-	-
Duration (>=18 && <=26)		0 backfills
-	-	-
Duration (>=18 && <=28)		1 backfills
-	-	-
Duration (>=16 && <=28)		2 backfills

---

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

• Yes (please specify the tool below)

Not generated by AI, consulted the approach using it.

---

• 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.

[subhramit]

Not a thorough review but the overall direction looks okay to me. Thanks especially for the screenshots.
A committer will take a closer look soon.
Meanwhile, some pointers -

1. Please go through the project's contributing guidelines. Here, rebasing is preferred over back-merging main.
2. (more of a nit) the commit messages are too generic and not helpful. https://cbea.ms/git-commit/ can be a good resource.

[bbovenzi]

Looks like some static check failures

[ydsakshi]

@subhramit @bbovenzi Thanks for the quick review !

@bbovenzi Regarding static checks failure, they are passing now.