CAMEL-23603 - Fix JDK 25 build on CI due to JSpecify Nullable

[apupier]

compilation error

it is working on other JDK versions right now because the nullaway/Jspecify is not activated on the version of JDK used on the CI. Version on Jenkins CI:

• openjdk version "21.0.4" 2024-07-16 LTS
• OpenJDK 64-Bit Server VM Temurin-17.0.12+7 (build 17.0.12+7, mixed mode, sharing)

Minimal version to have the nullaway/jspecify activated:

• 21.0.8+
• 17.0.19+

The jspecify/nullaway doesn't support the maven.compiler.fork=true for our project for unknown reason.

I have not found the reason why this option was provided previously.

I checked in the release guide and this option is not used.

Description

Target

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

• 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 although they are normally detected and executed by CI.
• You can label PRs using 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.