NIFI-15730 - Bump Box SDK to 5.5.0, Commons Net to 3.13.0, gRPC to 1.80.0, and others

[pvillard31]

Summary

NIFI-15730 - Bump Box SDK to 5.5.0, Commons Net to 3.13.0, gRPC to 1.80.0, and others

• Box SDK from 5.4.0 to 5.5.0 - https://github.com/box/box-java-sdk/releases/tag/v5.5.0
• Docker Java API from 3.7.0 to 3.7.1 - https://github.com/docker-java/docker-java/releases/tag/3.7.1
• Spring Integration from 7.0.3 to 7.0.4 - https://github.com/spring-projects/spring-integration/releases/tag/v7.0.4
• gRPC from 1.79.0 to 1.80.0 - https://github.com/grpc/grpc/releases
• ICU4J from 78.2 to 78.3 - https://github.com/unicode-org/icu/releases/tag/release-78.3
• FlywayDB from 12.1.0 to 12.1.1 - https://github.com/flyway/flyway/releases/tag/flyway-12.1.1
• JLine from 4.0.4 to 4.0.7 - https://github.com/jline/jline3/releases/tag/4.0.7
• AWS SDK BOM from 2.42.14 to 2.42.16 - https://github.com/aws/aws-sdk-java-v2/blob/master/CHANGELOG.md
• Apache Commons Net from 3.12.0 to 3.13.0 - https://commons.apache.org/proper/commons-net/changes.html#a3.13.0
• Test Containers from 2.0.3 to 2.0.4 - https://github.com/testcontainers/testcontainers-java/releases/tag/2.0.4

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 contains commits signed with a registered key indicating Verified status

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
  • JDK 25

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