[CI] SearchResponseTests testFromXContentWithFailures failing

[elasticsearchmachine]

Build Scans:

• elasticsearch-periodic #6313 / java8_java-matrix
• elasticsearch-periodic #6194 / openjdk20_java-matrix

Reproduction Line:

./gradlew ':server:test' --tests "org.elasticsearch.action.search.SearchResponseTests.testFromXContentWithFailures" -Dtests.seed=9D7D82E60A161AD0 -Dtests.locale=is-IS -Dtests.timezone=America/Tortola -Druntime.java=8

Applicable branches:
7.17

Reproduces locally?:
N/A

Failure History:
See dashboard

Failure Message:

com.fasterxml.jackson.dataformat.yaml.JacksonYAMLParseException: The incoming YAML document exceeds the limit: 3145728 code points.
 at [Source: (ByteArrayInputStream); line: 71157, column: 49]

Issue Reasons:

• [7.17] 2 failures in test testFromXContentWithFailures (0.3% fail rate in 758 executions)
• [7.17] 2 failures in pipeline elasticsearch-periodic (11.1% fail rate in 18 executions)

Note:
This issue was created using new test triage automation. Please report issues or feedback to es-delivery.

[elasticsearchmachine]

Pinging @elastic/es-search (Team:Search)

[elasticsearchmachine]

Pinging @elastic/es-search-foundations (Team:Search Foundations)

[cbuescher]

Found a few more of these failures e.g. in "AggregationsTests", but only on 7.17 and the first ones in the last two months on Jan 29th, i.e. https://gradle-enterprise.elastic.co/s/ofpgn2i4tdohq
Labeling as low risk because I think this is likely a test item setup issue that for some reason is able to now hit the limit of YAML parsing document sizes.

[cbuescher]

The 3Mb yaml limit apparently comes via snakeyaml and was introduced in 1.32, which we have been using since 7.17.7 for a while