NIFI-12323 Configure StreamReadConstraints on the ObjectMapper used b…

[bbende]

…y StandardDataFlow

Summary

NIFI-12323

Tracking

Please complete the following tracking steps prior to pull request creation.

Issue Tracking

• Apache NiFi Jira issue created

Pull Request Tracking

• Pull Request title starts with Apache NiFi Jira issue number, such as NIFI-00000
• Pull Request commit message starts with Apache NiFi Jira issue number, as such NIFI-00000

Pull Request Formatting

• Pull Request based on current revision of the main branch
• Pull Request refers to a feature branch with one commit containing changes

Verification

Please indicate the verification steps performed prior to pull request creation.

Build

• Build completed using mvn clean install -P contrib-check
  • JDK 21

Licensing

• New dependencies are compatible with the Apache License 2.0 according to the License Policy
• New dependencies are documented in applicable LICENSE and NOTICE files

Documentation

• Documentation formatting appears as expected in rendered files

[exceptionfactory]

Thanks for the change @bbende. Although it is somewhat of an edge case to have large string values for JSON elements in the flow configuration, this makes sense for scenarios with scripted components or other reference items. Given that the application manages the content of the JSON directly, this change seems reasonable and restores the behavior prior to Jackson 2.14. +1 merging