Factorize all the aggregator, forwarder and sender code used to send container_lifecycle, container_image and sbom payloads.

[L3n41c]

What does this PR do?

Leverage the generic “EventPlatform” pipeline in the agent in order to factorize the aggregator, forwarder and sender code that was used to send the container_lifecycle, container_image and sbom payloads.

Motivation

Get rid of duplicated pieces of code.

Additional Notes

The contimage and sbom parts were introduced by #14962 and were inspired by the contlcycle one.
All three are replaced by the generic EventPlatform pipeline in this PR.

The new parameters for the “EventPlatform” pipeline were added in pkg/epforwarder/epforwarder.go

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

Enable container_image and sbom with this snippet of values.yaml file for the public Helm chart:

datadog:
  env:
    - name: DD_CONTAINER_IMAGE_COLLECTION_METADATA_ENABLED
      value: "true"
    - name: DD_CONTAINER_IMAGE_COLLECTION_SBOM_ENABLED
      value: "true"
    - name: DD_CONTAINER_IMAGE_ENABLED
      value: "true"
    - name: DD_SBOM_ENABLED
      value: "true"
  confd:
    container_image.yaml: |
      init_config:
      instances:
        - chunk_size: 1
          new_images_max_latency_seconds: 10
          periodic_refresh_seconds: 60
    sbom.yaml: |
      init_config:
      instances:
        - chunk_size: 1
          new_sbom_max_latency_seconds: 10
          periodic_refresh_seconds: 60

and validate that container images are still visible in the app.

Reviewer's Checklist

• If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
• Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
• A release note has been added or the changelog/no-changelog label has been applied.
• Changed code has automated tests for its functionality.
• Adequate QA/testing plan information is provided if the qa/skip-qa label is not applied.
• At least one team/.. label has been applied, indicating the team(s) that should QA this change.
• If applicable, docs team has been notified or an issue has been opened on the documentation repo.
• If applicable, the need-change/operator and need-change/helm labels have been applied.
• If applicable, the k8s/<min-version> label, indicating the lowest Kubernetes version compatible with this feature.
• If applicable, the config template has been updated.

[paulcacheux]

LGTM for team/agent-security related files

[NouemanKHAL]

Approved for cmd/cluster-agent-cloudfoundry/subcommands/run/command.go owned by @DataDog/platform-integrations

[dineshg13]

LGTM from @DataDog/opentelemetry perspective.

[clamoriniere]

🚀