Updating Docs For DiskBBQ Format

[john-wagster]

No description provided.

[elasticsearchmachine]

Pinging @elastic/es-search-relevance (Team:Search Relevance)

[elasticsearchmachine]

Pinging @elastic/core-docs (Team:Docs)

[john-wagster]

waiting on feature flag removal for bbq_disk

[github-actions]

🔍 Preview links for changed docs

• docs/reference/elasticsearch/mapping-reference/dense-vector.md
• docs/reference/elasticsearch/rest-apis/retrievers/knn-retriever.md
• docs/reference/query-languages/query-dsl/query-dsl-knn-query.md

[github-actions]

ℹ️ Important: Docs version tagging

👋 Thanks for updating the docs! Just a friendly reminder that our docs are now cumulative. This means all 9.x versions are documented on the same page and published off of the main branch, instead of creating separate pages for each minor version.

We use applies_to tags to mark version-specific features and changes.

Expand for a quick overview

When to use applies_to tags:

✅ At the page level to indicate which products/deployments the content applies to (mandatory)
✅ When features change state (e.g. preview, ga) in a specific version
✅ When availability differs across deployments and environments

What NOT to do:

❌ Don't remove or replace information that applies to an older version
❌ Don't add new information that applies to a specific version without an applies_to tag
❌ Don't forget that applies_to tags can be used at the page, section, and inline level

🤔 Need help?

• Check out the cumulative docs guidelines
• Reach out in the #docs Slack channel

[benwtrent]

we should wait until we remove the feature flag. But good to get the PR open now :).

We should likely have a section "When to use this..." in one of our pages.

[leemthompo]

Thanks for using the version tags @john-wagster 🏅 👍

Just couple suggestions to use inline, rather than section-level tags :)

[john-wagster]

closed in favor of #135299