[Fleet] Add preset_counts to agent_per_output_type telemetry

[kpollich]

Summary

Closes #172818

Adds a preset_counts property to the agents_per_output_type record in the Fleet Usage telemetry, e.g.

[
  {
    output_type: 'elasticsearch',
    count_as_data: 5,
    count_as_monitoring: 5,
    preset_counts: { balanced: 2, custom: 1, latency: 0, scale: 0, throughput: 1 }
  },
  { output_type: 'logstash', count_as_data: 1, count_as_monitoring: 0 },
  { output_type: 'kafka', count_as_data: 0, count_as_monitoring: 1 },
  {
    output_type: 'remote_elasticsearch',
    count_as_data: 1,
    count_as_monitoring: 1,
    preset_counts: { balanced: 0, custom: 0, latency: 0, scale: 1, throughput: 0 }
  }
]

[elasticmachine]

Pinging @elastic/fleet (Team:Fleet)

[apmmachine]

🤖 GitHub comments

Expand to view the GitHub comments

Just comment with:

• /oblt-deploy : Deploy a Kibana instance using the Observability test environments.
• /oblt-deploy-serverless : Deploy a serverless Kibana instance using the Observability test environments.
• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[nchaulet]

LGTM 🚀 you should probably have a follow up PR in telemetry to add the mappings

[kibana-ci]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: 8a98ce0

Failed CI Steps

• Detection Engine - Security Solution Cypress Tests #6

Metrics [docs]

✅ unchanged

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

cc @kpollich

[juliaElastic]

@kpollich I believe this should be backported to 8.12