Play JSON 2.10.8

Noteworthy improvements

#1226 [2.10.x] Avoid running out of memory when parsing heavily nested arrays or objects by @mkurz
- We now limit the maximum allowed nesting depth of JSON structures (arrays, objects, or a mix of both) to 1000. This limit can be adjusted using the system property play.json.parser.maxNestingDepth. We assume a depth of 1000 should be more than sufficient for virtually all real-world use cases.
  
  This change helps prevent both potential OutOfMemoryErrors and StackOverflowErrors. The latter, however, is not a concern for Play JSON, since it already uses a @tailrec-optimized parsing method. As a result, Play JSON is not affected by CVE-2025-52999, which specifically addresses StackOverflowError risks. This improvement is simply an additional safety measure.

#1226 [2.10.x] Avoid running out of memory when parsing heavily nested arrays or objects by @mkurz
- We now limit the maximum allowed nesting depth of JSON structures (arrays, objects, or a mix of both) to 1000. This limit can be adjusted using the system property play.json.parser.maxNestingDepth. We assume a depth of 1000 should be more than sufficient for virtually all real-world use cases.
  
  This change helps prevent both potential OutOfMemoryErrors and StackOverflowErrors. The latter, however, is not a concern for Play JSON, since it already uses a @tailrec-optimized parsing method. As a result, Play JSON is not affected by CVE-2025-52999, which specifically addresses StackOverflowError risks. This improvement is simply an additional safety measure.