fix(ui): filter out fields with disableListFilter in whereBuilder prior to adding conditions

[akhrarovsaid]

What?

This PR fixes an issue with the WhereBuilder where if the first field in a collection had disableListFilter enabled, the select in that fields Condition would be rendered disabled, making it impossible to query docs in list view.

Why?

To allow users to query their documents while still being able to set disableListFilter on fields regardless of where they are in the collection hierarchy.

How?

By filtering out unfilterable fields earlier in WhereBuilder and Condition components.

Fixes #10110

Before:
Dashboard-wherebuilder-before--Payload.webm

After:
Dashboard-wherebuilder-after--Payload.webm

[DanRibbens]

Thanks, looks good!

[DanRibbens]

I'm not sure what is happening in CI, the e2e that is failing is running for me locally. Good job.

EDIT: I commented too soon. This one is failing for me locally test/fields/collections/Text/e2e.spec.ts should disable field when admin.disableListFilter is true but still exists in the query

[DanRibbens]

I couldn't get this change to work exactly with existing functionality when the filter is set from a query param. I opened a new PR instead: #10267

[akhrarovsaid]

@DanRibbens Yeah, it seems that with this PR the last element in the WhereBuilder condition remains enabled instead of disabled as that test was expecting. That particular test was also moved to admin/e2e/list-view/e2e.spec.ts it seems.

Closing in favor of yours. Thanks for working with me here though, appreciate it.