GEOMESA-161 antimeridian query fixes

Here is my progress on GEOMESA-161, I have "working" anti-meridian fixes for BBOX, Overlaps, Within, and Intersects. Only Within and BBOX have naive tests written. I use hunter's code from a few days ago to do the anti-meridian splitting, which will change I guess depending on if we end up using spatial4j or not. Also at the moment BBOX is using a deprecated function `op.getSRS`, is there a better way of getting a BoundingBox (geotools) out of a vividsolutions Geometry? 
[question] Shouldn't we be able to wrap most of the new code in this block into a routine that is shared between `visitBBOX` and `visitBinarySpatialOp`?  The differences -- that BBOX is always a rectangle, and BinarySpatialOp is always interpreted as a polygon -- seem insubstantial for our purposes.