fix filter mechanism

With ba7f5789bbbcab95d7a655f6ec50a97b731b40d5 no $result was available
anymore.

�� Automatic code style fixes

fix numeric values in filter control. #665

fix header configuration for filter component

make filter syntax use the disabling of dynamic parameters

Also some more style improvements

refactoring dynamic parameter handling, part 3

This moves SQL building into it's own class, splitting it into separate
methods. This allows for reusing the filter handling a second time to
separate

refactoring dynamic parameter handling, part 3

This moves SQL building into it's own class, splitting it into separate
methods. This allows for reusing the filter handling a second time to
separate out the dynamic filters.

Still no work on tests

show more ...

change the way filters are rendered

Instead of a form, now links are used that immeadiately apply a selected
filter. To construct the link, the type's renderTagCloudLink() method is
reused.

Still t

change the way filters are rendered

Instead of a form, now links are used that immeadiately apply a selected
filter. To construct the link, the type's renderTagCloudLink() method is
reused.

Still to do:

* make it possible to apply multiple filters (this might need some
adjustments on the renderTagCloudLink() method signature)
* do ensure that one selected filter does not collapse all filter
possibilities. Cloud currently does this by implementing it's own
SearchConfig in SearchCloud, but that seems to be limited to handling
a single schema and field. I think it would make more sense to be able
enable/disable the dynamic filter handling for the standard
SearchConfig
* Improve styling. This is currently just a very quick rendering on top
of <details>

show more ...

added filter for AggregationFilter::getAllColumnValues()

Also renames Filter to AggregationFilter