[beats receivers] Ensure tests exist that prove user provided collector components can co-exist with generated components in a Hybrid Agent #9932
Description
What happens if the user sets their own extensions in hybrid mode configuration? We currently merge these naively, so we'd override either ours or theirs. We need to account for this in the otel manager. This isn't really an issue with this PR, but adding extensions here will actually make triggerring it possible.
The particular concern here is that user defined extensions can be merged correctly now that we are generate auth extensions by default, but we should in general verify that all possible collector components are handled correctly.
receivers:
processors:
exporters:
connectors:
extensions:
service:
telemetry:
pipelines:Acceptance Criteria
A test exists showing that an elastic-agent.yml containing one of each of the collector components above in addition to agent.monitoring, inputs, and outputs sections configured to use beats receivers is correctly merged into a final opentelemetry collector configuration that runs without errors or conflicts.