Reframe 'Audit Elasticsearch search queries' now that query logging exists

## Context

Raised in https://github.com/elastic/docs-content/pull/5039#issuecomment-4341782933.

**Impacted page:** https://www.elastic.co/docs/deploy-manage/security/logging-configuration/auditing-search-queries

**Related PR:** https://github.com/elastic/docs-content/pull/5039 (query logging)

## Problem

Now that query logging provides an official way to trace search queries and tie them to a user, the "Audit Elasticsearch search queries" page is misleading. The audit feature described on that page actually surfaces **any request body**, not only search query payloads. With query logging available, we should no longer position audit logging as the way to trace search queries.

## Definition of done

- Rename the page to something more generic like "Audit Elasticsearch HTTP payloads"
- Remove search-query-specific framing from the content
- Point readers to query logging as the recommended approach for tracing search queries