[8.18](backport #7172) Use elastic apm connector to replace other apm components

[mergify]

What does this PR do?

The PR replaces lsminterval processor and signaltometrics connector with the newly introduced elasticapm connector which wraps both the processor and the connector with the required APM configurations.

In addition, the PR also removes aggregation for metrics pipeline as required by elastic/opentelemetry-collector-components#390

The PR is same as #6937 but for 9.0 branch since the upgrade of otel components to version 0.120.0 has been merged to 9.0 already however, the main PR is still pending.

Why is it important?

To centralize all APM components and configurations a new connector component called elasticapmconnector was recently introduced. The component encapsulates the signaltometrics connector and the lsminterval connector along with the required configurations for APM.

To handle metrics-only services correctly for the UI.

Checklist

• I have read and understood the pull request guidelines of this project.
• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files
  - [ ] I have added tests that prove my fix is effective or that my feature works
  - [ ] I have added an entry in ./changelog/fragments using the changelog tool
  - [ ] I have added an integration test or an E2E test

Disruptive User Impact

How to test this PR locally

Related issues

• Closes: https://github.com/elastic/opentelemetry-dev/issues/750
• Closes: [elasticapm] Remove service_summary metric for metrics-only services opentelemetry-collector-components#390

Questions to ask yourself

• How are we going to support this in production?
• How are we going to measure its adoption?
• How are we going to debug this?
• What are the metrics I should take care of?
• ...

---

This is an automatic backport of pull request #7172 done by [Mergify](https://mergify.com).

[mergify]

Cherry-pick of efeb73b has failed:

On branch mergify/bp/8.18/pr-7172
Your branch is up to date with 'origin/8.18'.

You are currently cherry-picking commit efeb73bf2.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   deploy/helm/edot-collector/kube-stack/README.md
	modified:   deploy/helm/edot-collector/kube-stack/values.yaml
	modified:   internal/pkg/agent/cmd/testdata/otel/components-output.yml
	modified:   internal/pkg/otel/components.go
	modified:   internal/pkg/otel/samples/darwin/logs_metrics_traces.yml
	modified:   internal/pkg/otel/samples/linux/logs_metrics_traces.yml
	modified:   internal/pkg/otel/testdata/all-components.yml

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   NOTICE.txt
	both modified:   go.mod
	both modified:   go.sum
	both modified:   internal/pkg/otel/README.md

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

[elasticmachine]

Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane)

[lahsivjar]

LGTM!

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 0fcf60d

History

• 💔 Build #18914 failed 1f3a1fe

cc @lahsivjar @swiatekm