chore(ci): warn when /component-test has disabled integration tests

[gnodet]

Summary

After /component-test runs, the action now scans the tested modules for tests annotated with @DisabledIfSystemProperty(named = "ci.env.name"). If any are found, a warning is appended to the result comment:

⚠️ Some integration tests are disabled on GitHub Actions (@DisabledIfSystemProperty(named = "ci.env.name")) and require manual verification:

• components/camel-couchbase: 5 test(s) disabled on GitHub Actions

This addresses the issue where /component-test reports success but no ITs actually ran (e.g., couchbase, ollama), giving a false sense of validation.

Example output

On success with disabled tests:

✅ /component-test camel-couchbase tests passed successfully.

⚠️ Some integration tests are disabled on GitHub Actions ...

On failure with disabled tests:

❌ /component-test camel-couchbase tests failed. check the logs

⚠️ Some integration tests are disabled on GitHub Actions ...

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