Currently, if geo context is represented by something other than
geo_point or an object with lat and lon fields, the parsing of it
as a geo context can result in ignoring the context altogether,
returning confusing errors such as number_format_exception or trying
to parse the number specifying as long-encoded hash code. It would also
fail if the geo_point was stored.

This commit makes the deprecates creation of geo contexts without
correct path fields. And it fixes the issue when geo_point is stored.
It is a 6.x version of elastic#32821.

…-geo-context-path-mapping-time-6x

…-geo-context-path-mapping-time-6x

…-geo-context-path-mapping-time-6x