[9.2] (backport #10268) [AutoOps] Provide Sample Configuration to Debug Data

[mergify]

This provides a separate OTel configuration to allow users to better understand what data they are shipping with the AutoOps ES module.

What does this PR do?

This adds a new OTel configuration available for every OS that helps users to understand what data the AutoOps ES module exports.

Why is it important?

Many users have asked what data is collected by AutoOps and this helps them to explore it locally before shipping it anywhree.

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 added an entry in ./changelog/fragments using the changelog tool

Disruptive User Impact

None. This adds a new, optional configuration that the user can run to better understand AutoOps.

How to test this PR locally

Run the Elastic Agent against an Elasticsearch cluster.

./elastic-agent --config otel_samples/autoops_es_debug.yml

You will want to supply these environment variables (with values filled in relevant to your environment):

# Values are examples and have no effect other than to appear in output unchanged
AUTOOPS_TEMP_RESOURCE_ID=example-id
AUTOOPS_TOKEN=example_token

# Values must work:
AUTOOPS_ES_URL=https://localhost:9200

# Username / Password _OR_ API Key
AUTOOPS_ES_USERNAME=my-username
AUTOOPS_ES_PASSWORD=my-secure-password

AUTOOPS_ES_API_KEY=myapikey==

---

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

[elasticmachine]

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

[elasticmachine]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: 36e847b

Failed CI Steps

• x86_64:sudo: default

cc @pickypg