Grid: Add support for setting a filtered data provider

[peholmst]

Fixes #3842.

This is my outcome from the AI workshop. Claude wrote all the code according to my specifications. This PR:

• Introduces a new set of methods, setItemsWithFilter that accept a fetch callback, a fetch/count callback pair, and a backend data provider, respectively, with a non-void filter type.
• Introduces a new GridLazyFilterDataView type that makes it possible to set a filter.

This maintains backwards compatibility with the existing methods and types without introducing new generic type parameters.

[CLAassistant]

All committers have signed the CLA.

[sonarqubecloud]

Quality Gate passed

Issues
5 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[sissbruecker]

I'm trying to figure out what the intended benefit here is, or how much of a benefit compared to adding to the API confusion around setItems / setItemsPageable / setDataProvider.

So for example, how is this approach better than this:

var filterableDataProvider = new CallbackDataProvider<String, String>(query -> Stream.empty(), query -> 0)
        .withConfigurableFilter();

grid.setItems(filterableDataProvider);

filterableDataProvider.setFilter("test");

[peholmst]

The approach you suggested requires a count callback. If I want to use just a fetch callback, I'd have to write:

var filterableDataProvider = new CallbackDataProvider<String, String>(
  query -> Stream.empty(),
  query -> { throw new UnsupportedOperationException(""); }
).withConfigurableFilter();

grid.setItems(filterableDataProvider);
grid.getLazyDataView().setItemCountUnknown();