NIFI-15607 - Bump Spring Security to 7.0.3, JUnit to 6.0.3, Logback to 1.5.32, and others

[pvillard31]

Summary

NIFI-15607 - Bump Spring Security to 7.0.3, JUnit to 6.0.3, Logback to 1.5.32, and others

• Spring Vault from 4.0.0 to 4.0.1 - https://github.com/spring-projects/spring-vault/releases/tag/4.0.1
• Spring Data Redis from 4.0.2 to 4.0.3 - https://github.com/spring-projects/spring-data-redis/releases/tag/4.0.3
• Spring LDAP from 4.0.1 to 4.0.2 - https://github.com/spring-projects/spring-ldap/releases/tag/4.0.2
• Spring Security from 7.0.2 to 7.0.3 - https://github.com/spring-projects/spring-security/releases/tag/7.0.3
• JUnit from 6.0.2 to 6.0.3 - https://github.com/junit-team/junit-framework/releases/tag/r6.0.3
• Logback from 1.5.29 to 1.5.32 - https://github.com/qos-ch/logback/releases/tag/v_1.5.32
• Amazon Kinesis Client from 3.3.0 to 3.4.0 - https://github.com/awslabs/amazon-kinesis-client
• Google Cloud SDK BOM from 26.75.0 to 26.76.0 - https://github.com/googleapis/java-cloud-bom/releases/tag/v26.76.0
• AWS SDK BOM from 2.41.27 to 2.41.29 - https://github.com/aws/aws-sdk-java-v2/blob/master/CHANGELOG.md

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