chore(ci): Fix parent POM dependency change detection

[gnodet]

Summary

The detect-dependencies CI action was never finding affected modules for dependabot PRs that bump versions in parent/pom.xml.

Root cause: The script searched for ${property-name} (e.g., ${jaxb-impl-version}) in module pom.xml files. This never matches because modules inherit managed versions from the parent's <dependencyManagement> without referencing the property directly — they just declare <artifactId>jaxb-impl</artifactId> without a <version>.

Fix: New approach that maps properties to artifacts to modules:

1. Diff parent/pom.xml to find changed property names
2. Parse parent/pom.xml to find which <artifactId> uses each property as its <version> in <dependencyManagement>
3. Search module pom.xml files for those artifact IDs
4. Run tests for affected modules

Example: For PR #22019 (jaxb-impl-version bump), the old script found 0 modules. The new script correctly finds camel-drill, camel-ibm-cos, and camel-swift.

Additional improvements

• Posts a PR comment summarizing which modules were tested and whether tests passed/failed
• Writes step summary output
• Removes the overly restrictive version|dependency|artifact keyword filter on property names
• Adds proper skip-mvnd-install input to avoid reinstalling mvnd
• Only runs on non-experimental matrix builds (skips JDK 25)
• Caps at 50 modules to avoid excessive test runs

Test plan

• Verified locally that jaxb-impl-version → jaxb-impl → camel-drill, camel-ibm-cos, camel-swift detection works
• CI will validate the script runs without errors
• Next dependabot PR touching parent/pom.xml will exercise the full flow

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

[squakez]

Example: For PR #22019 (jaxb-impl-version bump), the old script found 0 modules. The new script correctly finds camel-drill, camel-ibm-cos, and camel-swift.

For the record, this assumption is wrong. Those components are not using the dependency, but they are excluding it, see:

                <exclusion>
                    <groupId>com.sun.xml.bind</groupId>
                    <artifactId>jaxb-impl</artifactId>
                </exclusion>

The script was working correctly and this change was merged based on a wrong assumption.