Add support for RFC 10008 - HTTP QUERY

Describe the feature

The HTTP QUERY method has now been accepted by the IETF as a proposed standard - https://datatracker.ietf.org/doc/html/rfc10008. It has also been accepted as part of the OpenAPI 3.2 standard - https://www.openapis.org/blog/2025/09/23/announcing-openapi-v3-2

Since the purpose of QUERY is to accept a body payload rather than the confusion of whether to use POST for idempotent queries that are longer than a standard GET query string allows, it needs adding to the set of payloadMethods alongside PATCH, POST, PUT, and DELETE.

Without this change, the raw JS object will be passed through to fetch, causing either a TypeError or, potentially, for [object Object] to be sent instead.

I'll shortly open a one-line PR for this change.

Additional information

• Would you be willing to help implement this feature?

Search the codebase for the payloadMethods list alongside the existing PATCH, POST, PUT, and DELETE handling, then read how its values are passed to fetch. Add QUERY to that list and verify that a raw JavaScript object is handled as a request body rather than passed directly to fetch.