Expression filters

[tobrun]

WIP, this PR provides Android binding integration for #11251:

• remove old Filter.java API
• integrate setFilter(Expression filter)
  • update MapboxMap#queryRenderedFeatures
  • update Source#querySourceFeatures on source types
  • update Layer#setFilter on layer types (code-gen)
• add getFilter
  • manage state corretly when no filter is availlable (java.lang.Error: in get())
• integrate generated instrumentation test for set/get filter
• migrate test app code to expression syntax

[ivovandongen]

Are there any other object types we expect here? Should we deal with those cases?

[ivovandongen]

Can we type this more specific than Object?

[tobrun]

@ivovandongen thank you for the review, I addressed your comments in 145e1e0. (FWIW flagging that most of the code in this PR will be refactored out with #11419 and #11420)

[vanshg]

I see that Filter.none has been removed with no explicit replacement (as well as Filter.notHas). Are there any plans on making those explicitly available, or will we have to go with something more verbose such as Expression.not(Expression.any) and Expression.not(Expression.has)?

[tobrun]

I see that Filter.none has been removed with no explicit replacement (as well as Filter.notHas). Are there any plans on making those explicitly available, or will we have to go with something more verbose such as Expression.not(Expression.any) and Expression.not(Expression.has)?

the latter