docs: Update exploring data in {es}

[bmorelli25]

Summary

This PR moves the "Exploring data in Elasticsearch" section to the "Manage storage" bucket. It also condenses some of the content into a single page within expandable boxes.

"Application metrics" being a sub-nested heading was the best solution I could think of. Open to other ideas.

[mergify]

This pull request does not have a backport label. Could you fix it @bmorelli25? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-7.x is the label to automatically backport to the 7.x branch.
• backport-7./d is the label to automatically backport to the 7./d branch. /d is the digit

NOTE: backport-skip has been added to this pull request.

[ghost]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2023-05-16T20:43:06.432+0000

• Duration: 2 min 16 sec

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

• /package : Generate and publish the docker images.

• /test windows : Build & tests on Windows.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[simitt]

IMO we'll need to rework the metrics docs for some reasons:

• the main question that we see raised is which metrics end up in service specific datastreams and which in the generic one
• irritation around the aggregated metrics

We'll need to better cover these topics, but without over-documenting it, as the concrete (aggregated) metrics data streams are considered an internal detail, that we might change, as long as the UI changes the queries in a compatible way.
Should we have an in-depth conversation for this topic on this PR, or do you prefer a follow up issue to not slow down the structural changes?

[bmorelli25]

👍 Makes sense. I'd prefer to move the conversation to a separate issue.

[mergify]

This pull request is now in conflicts. Could you fix it @bmorelli25? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b ft-explore upstream/ft-explore
git merge upstream/main
git push upstream ft-explore