[WIP] DO NOT MERGE!!!! - Springboot 4.0.x upgrade

[nrknithin]

Kie-Issue: apache/incubator-kie-issues#2288

Related PRs

• Optaplanner: [WIP] DO NOT MERGE!!!! - Springboot 4.0.x upgrade  incubator-kie-optaplanner#3221
• Kogito Runtimes: [WIP] DO NOT MERGE!!!! - Springboot 4.0.x upgrade incubator-kie-kogito-runtimes#4270

Summary

Update version properties in build-parent/pom.xml to align with Spring Boot 4.0.x. Drools doesn't depend on Spring Boot directly, but downstream Apache KIE repos (kogito-runtimes, kogito-apps, kogito-examples) inherit these versions, so they need to match the spring-boot-dependencies:4.0.5 BOM.

What changed

jackson 2.21.1 → 2.21.2
jackson.databind 2.21.1 → 2.21.2
micrometer 1.14.12 → 1.16.4
hamcrest 2.2 → 3.0
junit-jupiter 5.13.4 → 6.0.3
junit-platform 1.13.4 → 6.0.3 (JUnit 6 uses unified versioning)
logback 1.5.25 → 1.5.32
h2database 2.3.232 → 2.4.240
commons-lang3 3.18.0 → 3.19.0
infinispan 15.0.21.Final → 15.2.6.Final
postgresql 42.7.8 → 42.7.10

Why

Spring Boot 4.0.5 ships these versions in its dependencies BOM. Aligning here prevents version-resolution conflicts in downstream repos that import both drools-build-parent and spring-boot-dependencies.

One subtle point: junit-platform had to go to 6.0.3, not 1.14.x. JUnit 6 unified the version numbering — junit-bom:6.0.3 pins both Jupiter and Platform to 6.0.3. Pairing Jupiter 6.0.3 with Platform 1.13.4 causes NoSuchMethodError at test discovery.

Verified with a full mvn clean install (all tests pass).

---

In drools-reliability/drools-reliability-infinispan/pom.xml & drools-reliability/drools-reliability-tests/pom.xml: added an <ignoreClass> entry for org.infinispan.commons.spi.OffHeapMemory and ThreadCreator (scoped to infinispan-commons-spi) to resolve a CI duplicate-class build failure introduced by the infinispan bump — at 15.2.6.Final upstream ships byte-identical copies of those two classes in both infinispan-commons and infinispan-commons-spi. Mirrors the existing infinispan-objectfilter exception in the same file.