feat(components): distinguish core processors from custom processors

[squakez]

PR to fix the behavior referred in CAMEL-23432 issue.

The main idea is to distinguish core processors from custom processors as the former should never be excluded during the generation of a telemetry trace, given that certain concrete telemetry technologies are instrumenting at a processor level.

TODO:

• provide design doc and migration doc
• Implement camel-telemetrydev
• Implement camel-opentelemetry2
• Implement camel-micrometer-observability
• Add parameter in CSB
• Add parameter in CQ

Description

Target

• I checked that the commit is targeting the correct branch (Camel 4 uses the main branch)

Tracking

• If this is a large change, bug fix, or code improvement, I checked there is a JIRA issue filed for the change (usually before you start working on it).

Apache Camel coding standards and style

• I checked that each commit in the pull request has a meaningful subject line and body.

• I have run mvn clean install -DskipTests locally from root folder and I have committed all auto-generated changes.

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