🐛 [cloud_firestore] Make Filter.or and Filter.and more flexible

[BuyMyBeard]

What feature would you like to see?

I have some issues with the current implementation of Filter.or() and Filter.and(). The current implementation declares every filter parameter as a positional parameter, and this prevents programmatic usage of Filter.

For example, I'd like to provide a list of AND filters directly. Looking at the queries limitations, this does remove the compile-time check for using more than 30 filters, but this is already undermined by the possibility of nesting filters.

In turn, some runtime checks could be added, to prevent joining more than 30 filters into a filter. It would also allow providing only one filter to Filter.or and Filter.and, making it equivalent to a normal filter. I am unsure how it should handle having no filters, whether is should either fail, make a query that returns nothing, or getting bypassed.

I'd like to contribute this feature, but I don't want to break existing usage. I'd like to get feedback on if this feature should be implemented with new named constructors, a different class or should replace the current usage.