[GEO] Fix for NPE enclosed in SearchParseException for a "geo_shape" fil...

...ter or query

This fix adds better error handling for parsing multipoint, linestring, and polygon GeoJSONs.  Current logic throws a NPE when parsing a multipoint, linestring, or polygon that does not comply with the GeoJSON specification. That is, if a user provides a single coordinate instead of an array of coordinates, or array of linestrings, the ShapeParser throws a NPE wrapped in a SearchParseException instead of a more useful error message.

Closes #8432
can we use ` == false` instead of `!` it's so much easier to read and  burned my fingers too often