fix: prevent StackOverflowError from deeply nested GeometryCollection in GeoJsonParser - #1699

googlemaps#1699 and googlemaps#1710 added nesting-depth guards, but they run on the tree that
Json.parseToJsonElement() has already fully materialised, so they act too late:
GeoJsonParser.parse() reads and materialises the whole untrusted document
before any check. A hostile layer can therefore still

  - overflow the parser stack with deep nesting (StackOverflowError) before the
    MAX_GEOMETRY_DEPTH=20 guard runs (contrast KmlParser, which bounds depth
    *during* streaming via DepthLimitingReader);
  - exhaust the heap with a wide, shallow document (OutOfMemoryError), which no
    depth guard addresses;
  - forward non-finite coordinates ("Infinity"/"NaN", accepted by
    String.toDouble()) straight into LatLng/LatLngBounds.

The first two throw java.lang.Error subclasses, so the catch (Exception) in
DataLayerLoader does not contain them and the host app crashes on load.

Bound the input up front, before parseToJsonElement:

  - readTextBounded() caps the characters read (configurable, default 10 MiB);
  - checkStructuralDepth() rejects raw '{'/'[' nesting beyond a limit in a
    single string-aware pass (configurable, default 512 - safe on small Android
    stacks, far above any legitimate GeoJSON);
  - parseCoordinates() rejects non-finite values.

Limits are constructor parameters with safe defaults, mirroring KmzParser.
Existing behaviour is preserved (incl. the googlemaps#1699 depth-200 GeometryCollection
test); adds tests for each case.

…ion (#1733)

* fix: bound untrusted GeoJSON input to prevent parser resource exhaustion

#1699 and #1710 added nesting-depth guards, but they run on the tree that
Json.parseToJsonElement() has already fully materialised, so they act too late:
GeoJsonParser.parse() reads and materialises the whole untrusted document
before any check. A hostile layer can therefore still

  - overflow the parser stack with deep nesting (StackOverflowError) before the
    MAX_GEOMETRY_DEPTH=20 guard runs (contrast KmlParser, which bounds depth
    *during* streaming via DepthLimitingReader);
  - exhaust the heap with a wide, shallow document (OutOfMemoryError), which no
    depth guard addresses;
  - forward non-finite coordinates ("Infinity"/"NaN", accepted by
    String.toDouble()) straight into LatLng/LatLngBounds.

The first two throw java.lang.Error subclasses, so the catch (Exception) in
DataLayerLoader does not contain them and the host app crashes on load.

Bound the input up front, before parseToJsonElement:

  - readTextBounded() caps the characters read (configurable, default 10 MiB);
  - checkStructuralDepth() rejects raw '{'/'[' nesting beyond a limit in a
    single string-aware pass (configurable, default 512 - safe on small Android
    stacks, far above any legitimate GeoJSON);
  - parseCoordinates() rejects non-finite values.

Limits are constructor parameters with safe defaults, mirroring KmzParser.
Existing behaviour is preserved (incl. the #1699 depth-200 GeometryCollection
test); adds tests for each case.

* test: make the deep-nesting test reproduce the overflow deterministically

The previous version of this test could pass on unpatched code for an
unrelated reason: with the nesting inside "coordinates", a parse that
survives the stack reaches parseCoordinates(), which calls jsonPrimitive
on a JsonArray and throws IllegalArgumentException - the very type the
test asserts.

Move the nesting under "bbox", a member the parser never dereferences,
so nothing can reject the document first, and run the parse on a thread
with an explicit 1 MB stack so the outcome does not depend on the stack
size of the thread the test framework happens to use. 50 000 levels
overflow that stack whether or not the parser is JIT-compiled, while the
structural-depth check rejects the document at nesting level 513 without
recursing at all. A small document is parsed first so that class loading
is not charged to the bounded stack.

On main this test now fails with StackOverflowError instead of passing.