Add Dag Run limit dropdown for Grid view page

[shubhamraj-git]

Closes: #47887

---

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in newsfragments.

[bbovenzi]

Sorry, I'm gonna close this one. We intentionally left the dagrunselect out of the grid view because it is redundant and only adds noise to the page.

This issue wants to change the limit parameter for our useGrid() query. Not adding a dag run dropdown

[shubhamraj-git]

@bbovenzi Oh, I see! I misread the issue. You mean having a dynamic query parameter as a dropdown, which controls the number of runs displayed, similar to how it worked in the older version.

For the older UI, I see the control was on central level, which also affects the runs list and grid view, in the new UI implementation, the State filter on the runs list tab don't affect the grid view. Are we keeping both out of sync intentionally ? In that case we will have a run count dropdown just for grid view?

I can continue the changes in this PR itself.

[jscheffl]

Testing I found a couple of glitches.

(1) The Grid is not displaying when I start a couple of runs. Might it be missing if some DAGs are just queued?

Can confirm. Might be an un-related bug. If any of the DAG runs is queued then the Grid is not displaying.

(2) Is a count is limit is seelcted, the clear button (x) is overlapping with the dropdown:

[bbovenzi]

@jscheffl does that queue issue happen in main?

[shubhamraj-git]

@jscheffl @bbovenzi Removed the placeholder and now it defaults to 10 and shows the same. Also removed the condition which displays it only on the grid view, since graph view have the list dag runs, which was always defaulting to 14, now instead it will be controlled via dropdown.

[jscheffl]

@jscheffl does that queue issue happen in main?

@bbovenzi I tested yesterday on this PR... which was "close" to main. But I noticed it a couple of days ago.
But can re-produce on main. Itis simple: Navigate to a DAG with grid view. Turn scheduling of. Trigger the DAG but take care that the triogger does not activate scheduling again. See that there is a queued run. Press F5. Grid is empty.

Console reveals a HTTP 500.
Stack trace on server looks like:

[jscheffl]

This PR looks good! LGTM!