NIFI-14960 - Bump Spring to 6.2.11, Jetty to 12.0.27, Protobuf to 4.32.1, and others

[pvillard31]

Summary

NIFI-14960 - Bump Spring to 6.2.11, Jetty to 12.0.27, Protobuf to 4.32.1, and others

• MongoDB Driver from 5.5.1 to 5.6.0 - https://github.com/mongodb/mongo-java-driver/releases/tag/r5.6.0
• Protobuf from 4.32.0 to 4.32.1 - https://github.com/protocolbuffers/protobuf/releases/tag/v32.1
• Spring Data Redis from 3.5.3 to 3.5.4 - https://github.com/spring-projects/spring-data-redis/releases/tag/3.5.4
• Checker-qual from 3.50.0 to 3.51.0 - https://github.com/typetools/checker-framework/releases/tag/checker-framework-3.51.0
• MariaDB Java Client from 3.5.5 to 3.5.6 - https://github.com/mariadb-corporation/mariadb-connector-j/releases/tag/3.5.6
• AWS SDK v2 from 2.33.5 to 2.33.8 - https://github.com/aws/aws-sdk-java-v2/blob/master/CHANGELOG.md
• Jetty from 12.0.26 to 12.0.27 - https://github.com/jetty/jetty.project/releases/tag/jetty-12.0.27
• Groovy from 5.0.0 to 5.0.1 - https://groovy-lang.org/changelogs/changelog-5.0.1.html
• Spring from 6.2.10 to 6.2.11 - https://github.com/spring-projects/spring-framework/releases/tag/v6.2.11

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 ./mvnw 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