Handle antimeridian / wrapX

[jampukka]

• Add support for bbox geometries crossing the antimeridian (or more generally some wrapX value, depends on projection)
• Logic is applied to both bbox query param as well as CQL2 bbox expressions (but not all spatial literals) appearing in filter query param
• bbox-crs is now handled before bbox
  • In-line with filter-crs. Made these changes much more readable.
  • More of a nice-to-know, but if you relied on this for some strange reason then act acoordingly
• Move logic and responsibility of reprojecting filtering geometries to storage CRS from data source level to parameter/core level
  • Same code used for all data sources
  • Easier to implement additional data sources
• Add two new configurable properties to SRIDCode: wrapXMin and wrapXMax
  • Do not set these if wrapping x makes no sense (true for most local projected systems)
    • Invalid bounding boxes with will return an exception
  • For CRS84/WGS84 the values are hard-coded at 180°/-180° and do not require any configuration
• Should fix issue Ensure bbox queries work correctly when bbox spanning the antimeridian #79