[ui] node eligibilty taken into consideration when clients list filtered to "ready"

[philrenaud]

On our clients list page, we abstract node readiness, eligibility, and draining status into one State filter.

This leads to situations where a user selects "Ready" and expects to see eligible nodes, but a node can technically be "ready" by status and marked ineligible for new tasks.

This seems confusing with the abstraction in place. As such, selecting "Ready" will not filter out any ineligible nodes.

In resolving this, we've made some updates to the way the State filter works, relative to the others:

• It is an "inclusive" filter, with all options selected by default (others are exclusive until something is clicked)
• query parameters from it are individually appended to the URL, where in other dropdowns a stringified array of all checked options is appended
• it includes subsections for Status, Eligibility, and Drain status, where others are single-subject filters.

We realize this creates an inconsistency, but felt like this represents a practical approach to making state filter behaviour here work as expected.

Resolves #18593

[github-actions]

Ember Test Audit comparison

	main	8495b46	change
passes	1540	1540	0
failures	0	0	0
flaky	0	0	0
duration	10m 48s 517ms	11m 00s 228ms	+11s 711ms

[gulducat]

I agree this likely aligns with user intent, as our placing "ready" next to "ineligible" in the drop-down, with no other explicitly positive option, suggests that "ready" = "eligible" 👍

[philrenaud]

Note: converting back to draft after realizing how much test logic is tied up in state/eligibility/drain status.
A more holistic approach in the future will look like this:

and untie eligibility/drain status as "status" concepts / list them as tags of the node name, rather than under "state" (which should be renamed Status, to match CLI/API)

[github-actions]

I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.