Upgrade Camel to spring-boot 4

[cunningt]

Description

This is a PR for spring-boot 4 upgrade work. It upgrades jackson to 2.20.2, it changes all components over to using camel-test-junit-6, and makes a number of other upgrades necessary for the move to spring boot 4.

Related issues :
https://issues.apache.org/jira/browse/CAMEL-22728
https://issues.apache.org/jira/browse/CAMEL-22729
https://issues.apache.org/jira/browse/CAMEL-22730

Target

• [ x] I checked that the commit is targeting the correct branch (Camel 4 uses the main branch)

Tracking

• If this is a large change, bug fix, or code improvement, I checked there is a JIRA issue filed for the change (usually before you start working on it).

Apache Camel coding standards and style

• I checked that each commit in the pull request has a meaningful subject line and body.

• [ x] I have run mvn clean install -DskipTests locally from root folder and I have committed all auto-generated changes.

[github-actions]

🌟 Thank you for your contribution to the Apache Camel project! 🌟

🤖 CI automation will test this PR automatically.

🐫 Apache Camel Committers, please review the following items:

• First-time contributors require MANUAL approval for the GitHub Actions to run

• You can use the command /component-test (camel-)component-name1 (camel-)component-name2.. to request a test from the test bot.

• You can label PRs using build-all, build-dependents, skip-tests and test-dependents to fine-tune the checks executed by this PR.

• Build and test logs are available in the Summary page. Only Apache Camel committers have access to the summary.

• ⚠️ Be careful when sharing logs. Review their contents before sharing them publicly.

[davsclaus]

if you keep this up to date then SB 4.0.1 has been released

[cunningt]

Updated to spring-boot 4.0.2, all checks passed on 2/4/2026. Will rebase and upgrade to spring-boot 4.0.3 after release (2/19/2026).

[Croway]

@cunningt I did some changes to the mvn test parent pom dependencies changed but I think that the gh runner cannot handle test execution of this many components in parallel with mvnd, this is why it is still failing. I tried the soap test locally, and it is successful