Revert "chore(ci): Fix parent POM dependency change detection (#22022)"

[gnodet]

Summary

Reverts the detect-dependencies CI action back to its original implementation (#22022). The reworked version is causing issues in CI. A proper fix will be done in #22247.

Known limitation

The original detect-test.sh searches for ${property-name} references in module pom.xml files to find affected modules. This works for ~78% of the version properties in parent/pom.xml (395 out of 504), which directly reference the property in their pom. However, ~22% of properties are only used through <dependencyManagement> inheritance and are not detected by this grep-based approach (e.g., caffeine-version, bytebuddy-version). This limitation will be addressed in #22247.

Test plan

• CI passes

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

If this is reverting the situation exactly to the same working version, then it's fine. However, I suggest to perform a test on a private fork before, to make sure that, indeed, given a change on a parent pom dependency, triggers the test on the affected modules.

[apupier]

same than @squakez

given recent experience, I think these kid of changes needs to be tested first

[gnodet]

Tested on the gnodet fork with a dnsjava-version bump (3.6.4 → 3.6.3). The detect-dependencies step correctly detected the change, found camel-dns as an affected module, and ran its tests successfully (22 tests, 0 failures).

Full CI run: https://github.com/gnodet/camel/actions/runs/23599119328

Claude Code on behalf of Guillaume Nodet