Provide mechanism to configure XContent parsing constraints (after update to Jackson 2.15.0)

[reta]

Is your feature request related to a problem? Please describe.
The OpenSearch used to have no constants (at least officially) on maximum fields sizes that could be uploaded using supported XContent types (JSON/CBOR/YAML/Smile). Since Jackson 2.15.0, there are streaming constraints in place.

Describe the solution you'd like
Provide the way to alter Jackson 2.15.0 streaming constraints for supported XContent types. Since all factories are initialized statically, the suggestion is to use system property opensearch.xcontent.string.length.max. The default has also been increased from ~5Mb to ~50Mb.

Describe alternatives you've considered
Lift the streaming constraints by setting the maximum string size to Integer.MAX_VALUE.

Additional context
#7286
FasterXML/jackson-core#1001 (comment)

[reta]

Documentation update opensearch-project/documentation-website#4089

[ylwu-amzn]

Thanks @reta , I see the Jackson 2.15.0 version bump also backported to 2.x branch #7300. Is that must have? This will introduce string length limit, which is a breaking change.If user store big strings in index, it will stop working after upgrading to 2.8. Should be fine to have this breaking change in major version release like 3.0, but should we keep BWC for minor version release (2.7 -> 2.8)?

[reta]

@ylwu-amzn we bumped the limit 10x to accomodate for such possible regression, however to your point, we may lift the content limit for 2.x branches.