NIFI-15380 - Bump Logback to 1.5.23, frontend plugin to 2.0.0, elastic to 9.2.3 and others

[pvillard31]

Summary

NIFI-15380 - Bump Logback to 1.5.23, frontend plugin to 2.0.0, elastic to 9.2.3 and others

• Elasticsearch Client from 9.2.2 to 9.2.3 - https://github.com/elastic/elasticsearch-java/releases/tag/v9.2.3
• QuestDB from 9.2.2 to 9.2.3 - https://github.com/questdb/questdb/releases/tag/9.2.3
• Spring Boot from 3.5.8 to 3.5.9 - https://github.com/spring-projects/spring-boot/releases/tag/v3.5.9
• FlywayDB from 11.19.0 to 11.19.1 - https://github.com/flyway/flyway/releases/tag/flyway-11.19.1
• Frontend Maven Plugin from 1.15.4 to 2.0.0 - https://github.com/eirslett/frontend-maven-plugin/blob/master/CHANGELOG.md
• AWS SDK BOM from 2.40.11 to 2.40.13 - https://github.com/aws/aws-sdk-java-v2/blob/master/CHANGELOG.md
• Logback from 1.5.22 to 1.5.23 - https://github.com/qos-ch/logback/releases/tag/v_1.5.23
• Exec Maven Plugin from 3.6.2 to 3.6.3 - https://github.com/mojohaus/exec-maven-plugin/releases/tag/3.6.3

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

[exceptionfactory]

Thanks @pvillard31, the upgrades look good, there is just a merge conflict to resolve, then this should be ready to go.

[pvillard31]

Done, thanks @exceptionfactory