Investigate anomaly detection config keys: `anomaly_detection.enabled` and `anomaly_detection.metrics.enabled`.

[jszwedko]

Problem

The core agent's comp/anomalydetection subsystem is gated by:

• anomaly_detection.enabled — activates the anomaly detection observer pipeline
• anomaly_detection.metrics.enabled — enables DogStatsD metric ingestion into the anomaly detection buffer

ADP has no anomaly detection component. It is unclear whether:

1. ADP is expected to feed metrics into an anomaly detection pipeline in the future, or
2. These keys are permanently outside ADP's scope because anomaly detection runs in the core agent.

What needs to happen

Clarify the intended architecture: does ADP need to forward metric samples to an anomaly detection subsystem, or does the core agent handle that separately from the DogStatsD forwarding path? Document the outcome as either Not Planned (with reason) or as a future IMPLEMENT item.