make typeFilter accept arbitrary sets of OSMType

[tyrasd]

This changes osm-type filters to

• make them work the same as the other filters (i.e. when called multiple times, the filters are intersected together). technically this is a breaking change compared to how this worked
• allow arbitrary set types to be supplied (not only EnumSets)
• made jdbc backends work with "no osm type" cases. (e.g. .osmType(EnumSet.noneOf(OSMType.class))).
• add unit tests

Checklist

• My code follows the code-style rules and I have checked on the static analyses and benchmark (if applicable) results
• I have commented my code
• I have written javadoc (required for public methods)
• I have added sufficient unit tests
• I have made corresponding changes to the documentation
• I have updated the CHANGELOG.md
• I have adjusted the examples and benchmark if necessary

[tyrasd]

thanks for the review @FabiKo117. The only reason why I was still reluctant to merge this is that it technically did break the way the method .osmType works compared to the current (v0.5.5) version.

But, on the other hand, according to our documentation (https://github.com/GIScience/oshdb/blob/master/documentation/manual/filters.md) the current (v0.5.5) code is actually wrong because it states the following which is currently not the case for the osmType filter:

Multiple filters can be applied after each other. The result will then contain any OSM elements that match all of the specified filters.

I'm changing this to a bugfix (from a breaking change), if you're ok with that?!

[FabiKo117]

I see.. from that point of view it is then actually a bugfix indeed.