CAMEL-23535: camel-api - batches 13-15: enhance class-level Javadoc for management, threading, and observability SPIs

[ammachado]

Description

Continues the systematic Javadoc improvement of core/camel-api started in CAMEL-23535.
This PR adds comprehensive class-level Javadoc to 19 SPI types across three logical batches:

Batch 13 — JMX Management SPIs
ManagementAgent, ManagementStrategy, ManagementStrategyFactory, ManagementNameStrategy,
ManagementObjectStrategy, ManagementObjectNameStrategy, ManagementMBeanAssembler,
ManagementInterceptStrategy

Documents the two-level management design (strategy = high-level coordinator, agent = low-level JMX bridge),
the ObjectName construction pipeline, and the instrumentation wrapping used for EIP statistics collection.

Batch 14 — Threading and Scheduling SPIs
ExecutorServiceManager, ThreadPoolProfile, ThreadPoolFactory, BackOffTimerFactory,
ScheduledPollConsumerScheduler, ReactiveExecutor

Documents the layering between the high-level manager (Camel concepts: profiles, naming, lifecycle)
and the low-level factory (pure JDK types, designed for JEE WorkManager substitution), plus the
reactive executor's async dispatch model.

Batch 15 — Observability SPIs
EventNotifier, EventFactory, Tracer, CamelLogger, CamelMDCService

Documents the producer/consumer split between EventFactory (mints event objects) and EventNotifier
(reacts to them), the Tracer before/after node interception model and standby mode, and
CamelMDCService's role in propagating MDC context across async continuation threads.

All types now include at least one link to the relevant Camel user manual page and @see cross-references
to related sibling types. No method signatures, annotations, or non-Javadoc code were changed.

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.

Claude Code on behalf of Adriano Machado

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

[orpiske]

Very good and important work that will benefit multiple projects in the ecosystem.

Thanks for this!

[github-actions]

🧪 CI tested the following changed modules:

• core/camel-api

ℹ️ Dependent modules were not tested because the total number of affected modules exceeded the threshold (50). Use the test-dependents label to force testing all dependents.

---

⚙️ View full build and test results