[8.17](backport #4854) Collect data with Elastic Cloud Native OpenTelemetry Endpoint

[mergify]

Description

This is a very rough outline of a potential Getting Started with Elastic Cloud Native OpenTelemetry Endpoint Guide. After we come to a consensus on the final guide, I will port to Markdown and our new documentation system.

Important

Reviewers: I've left comments and questions in the Asciidoc files. Please take a look and leave feedback.

Issues, People, etc.

• cc @jlind23 @mlunadia @vigneshshanmugam

closes #4851

---

This is an automatic backport of pull request #4854 done by Mergify.

[mergify]

Cherry-pick of ffa8978 has failed:

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

You are currently cherry-picking commit ffa89789.
  (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:
	new file:   docs/en/serverless/images/hosts-ui-otlp.png
	new file:   docs/en/serverless/images/resource-attrs.png
	new file:   docs/en/serverless/otlp-visualize.asciidoc
	new file:   docs/en/serverless/quickstarts/collect-data-with-native-otlp.asciidoc

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	deleted by us:   docs/en/serverless/index.asciidoc

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

[github-actions]

A documentation preview will be available soon.

• 🔨 Buildkite builds
• 📚 HTML diff
• 📙 Preview page

Request a new doc build by commenting

• Rebuild this PR: run docs-build
• Rebuild this PR and all Elastic docs: run docs-build rebuild

_{run docs-build is much faster than run docs-build rebuild. A rebuild should only be needed in rare situations.}

_{If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here.}