ci: pass maven-extra-args to incremental build for JDK 17 enforcer skip

[Croway]

relax the enforcer on the GH CI, so that we can keep testing with JDK17

---

The JDK 21+ enforcer rule added in #22608 correctly skips enforcement for JDK 17 in the full build (regen.sh uses MAVEN_EXTRA_ARGS), but the incremental test step and the quick dependency build step did not receive -Denforcer.phase=none, causing all JDK 17 CI jobs to fail.

Changes:

• Add maven-extra-args input to the incremental-build action
• Pass MAVEN_EXTRA_ARGS to all Maven/mvnd invocations in incremental-build.sh (main build commands and Scalpel validation)
• Pass MAVEN_EXTRA_ARGS to the quick dependency build step
• Pass matrix.maven_extra_args from the workflow to both steps

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