CAMEL-23274: Add incremental coverage to SonarCloud PR analysis

[gnodet]

CAMEL-23274

Summary

Replaces the hardcoded core-only coverage step with dynamic, incremental coverage for all PR-affected modules.

• Remove the hardcoded core test step from sonar-build.yml (no more stale module list to maintain)
• Add jacoco:report goal to the coverage profile in parent/pom.xml so each tested module generates its own XML report
• Update sonar.coverage.jacoco.xmlReportPaths to include both per-module and aggregated report paths
• Add dynamic coverage aggregation in incremental-build.sh: when core modules are detected among affected modules and -Dcoverage is active, automatically generate the aggregated report via the coverage module

Coverage strategy

Scope	Approach	Report path
Core modules (when affected)	Aggregated report via coverage -am (camel-core tests exercise classes across camel-core-model, camel-core-processor, etc.)	coverage/target/site/jacoco-aggregate/jacoco.xml
Components (when affected)	Per-module reports (each component's tests cover its own classes)	*/target/site/jacoco/jacoco.xml

Key improvements over previous approach:

• No hardcoded module list — core coverage aggregation triggers dynamically when any core/ module is in the PR diff
• No wasted CI time — core tests only run when core modules are actually affected
• Single test step — the incremental-build action handles everything

Test plan

• Verified on gnodet/camel#15 — SonarBuild passed, coverage aggregation triggered correctly when core module was affected
• Verify SonarCloud picks up both aggregated and per-module coverage data

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

[github-actions]

ℹ️ CI did not run targeted module tests (root project files changed).

---

⚙️ View full build and test results