Change default behaviour of spatial queries to use 'intersects' operator
While I agree with the need to precisely control the type of operator used in spatial queries (see #80), I realise I could require a large amount of work. I therefore suggest that we change the current implementation to use the 'intersects' operator (rather than the 'contains' as it seems to be the case).
Intersection appears to be a more useful and natural operator considering the nature of the data we are dealing with in OSDU.
Consider the case where a user requests geopolitical entities, seismic lines, seismic surveys, wells, bore trajectories, etc. within a polygon for a map display. One would expect that objects that are only partially inside the polygon to be displayed. Otherwise, it pre-supposes that the user already knows the geographical nature of what is being looked for.