Summary

Harden GeoJsonParser against resource exhaustion when parsing untrusted GeoJSON, by bounding the input before it is materialised. This closes the remaining gap left by the nesting-depth guards added in #1699 and #1710.

Problem

#1699 (MAX_GEOMETRY_DEPTH) and #1710 both guard against deeply nested input, but the GeoJSON guard runs during a second pass over the tree that Json.parseToJsonElement() has already fully materialised:

fun parse(inputStream: InputStream): GeoJsonObject? {
    val json = inputStream.bufferedReader().use { it.readText() }
    val jsonElement = Json.parseToJsonElement(json)   // whole document materialised here
    ...                                                // MAX_GEOMETRY_DEPTH is only checked after this

So for GeoJSON the guard acts too late. With an untrusted document a caller can still hit:

• Deep nesting → StackOverflowError. kotlinx-serialization's JSON reader recurses on nested arrays, so a few thousand nested arrays overflow the stack inside parseToJsonElement, before MAX_GEOMETRY_DEPTH is ever reached. (KmlParser avoids this by bounding depth during streaming with DepthLimitingReader; GeoJSON has no equivalent.)
• Wide, shallow document → OutOfMemoryError. A large flat array (e.g. a MultiPoint with millions of positions) materialises to far more heap than the source text, with no nesting for a depth guard to catch.
• Non-finite coordinates. "Infinity"/"NaN" are accepted by String.toDouble() and currently flow straight into LatLng/LatLngBounds.

The first two throw java.lang.Error subclasses, so the catch (e: Exception) in DataLayerLoader does not contain them and the failure propagates to the host app.

Fix

Bound the input up front, before parseToJsonElement():

• readTextBounded() — caps the number of characters read (configurable, default 10 MiB), so an oversized document is never fully materialised.
• checkStructuralDepth() — rejects raw {/[ nesting beyond a limit, in a single string-aware pass (configurable, default 512 — safe on small Android thread stacks, and far above any legitimate GeoJSON, whose structural depth stays well under 100 even with maximally nested geometries).
• parseCoordinates() — rejects non-finite values.

Both limits are constructor parameters with safe defaults, mirroring KmzParser's configurable zip-bomb limits (#1677). Rejected input throws IllegalArgumentException (an Exception), so DataLayerLoader degrades to a null layer instead of crashing.

Testing

Adds unit tests for each case (deep-nested arrays, excessively nested GeometryCollection, oversized input, non-finite coordinate). Existing behaviour is preserved, including the #1699 testDeeplyNestedGeometryCollectionDoesNotThrowStackOverflow case (depth 200 stays well within the structural limit and still parses).

Compatibility

GeoJsonParser's new parameters have defaults, so GeoJsonParser() continues to work unchanged for all existing (Kotlin) call sites (DataLayerLoader, GeoJsonLayer). No @JvmOverloads is added, matching the sibling KmzParser.