SERVER-139496Needs Scheduling
S2 heuristic counters have incorrect behavior on overflow
Our S2 geospatial third party library uses {{int}} counters for heuristics, like for when the cost of building a data structure indexing polygon vertices is likely to be amortized. * [S2Loop::num_find_vertex_calls_|https://github.com/10gen/mongo/blob/af22eb75e478f32fde03e16dfa748e4defa22055/src/third_party/s2/s2loop.h#L356] * [S2EdgeIndex::query_count_|https://github.com/10gen/mongo/blob/af22eb75e478f32fde03e16dfa748e4defa22055/src/third_party/s2/s2edgeindex.h#L243] For large collections