We include geometry details for GeoMatchExpression ($within, etc) and GeoNearMatchExpression ($geoNear) needed to distinguish predicates in plan cache entries. This needs to be done similarly for $_internalBucketGeoWithin.

This is problematic when caching single candidate plans (failure in timeseries_geonear_measurements.js). The plan cache key is the same for two queries, one of which is a "flat" 2d query (cannot use a geospatial index) and the other spherical (can use an index).