Correct QUERY verb docs: transactional middleware is dependency-based, not verb-based

[jeremydmiller]

Closes #3355.

A QUERY endpoint is wrapped in transactional middleware when it takes an IDocumentSession/DbContext under AutoApplyTransactions() — nothing in Wolverine keys off the HTTP verb. The WolverineQueryAttribute XML doc, the sample_wolverine_query_endpoint comment, and the "HTTP QUERY Method" docs tip all implied a verb-based exemption that doesn't exist, and the existing query_endpoint_is_not_wrapped_in_transactional_middleware test only exercised an endpoint with no dependencies at all, so it couldn't catch the misstatement.

Changes

• WolverineQueryAttribute XML doc (what users see in IntelliSense): states the actual rules — outbox middleware requires an IMessageBus/IMessageContext dependency; transactional middleware applies when the handler takes an IDocumentSession or DbContext; prefer IQuerySession (Marten) or [NonTransactional] (EF Core) for read-only QUERY endpoints.
• sample_wolverine_query_endpoint comment (surfaces in the docs via mdsnippets): attributes the endpoint's non-transactional status to the absence of a persistence dependency, not to the verb.
• docs/guide/http/endpoints.md tip: same correction, with the IQuerySession / [NonTransactional] guidance.
• Tests: two new WolverineWebApi QUERY endpoints — /search/audited taking IDocumentSession (asserted IsTransactional == true) and /search/readonly taking IQuerySession (asserted false) — pin the dependency-based rule so a verb-based special case can't be introduced silently. The existing test's comment now explains what it actually demonstrates.

Verification

• New + existing query_verb_support tests green (6/6)
• Full Wolverine.Http.Tests suite green: 813 passed / 0 failed / 10 skipped

🤖 Generated with Claude Code