feat: support HTTP QUERY operations - #4456

Reviewed changes

• Parser — adds query to the shared httpMethods list and parses QUERY operations from paths and webhooks, gated to >=3.2.0 (packages/shared/src/openApi/3.1.x/parser/{index,webhook}.ts).
• IR & spec types — adds query to IRPathItemObject and OpenAPIV3.PathItemObject, the '3.2.0' version literal, and the irPatterns regexes.
• Clients — adds query: makeMethodFn('QUERY') (and the SSE variant) across the bundled Angular/Axios/fetch/ky/next/Nuxt/ofetch clients and @hey-api/custom-client.
• Plugins — maps query to the query kind in defaultGetKind and generates client.query(...) SDK calls.
• Tests/snapshots — new 3.2.x.test.ts plus specs/3.2.x/http-query.yaml, parser version-boundary unit tests, a fetch runtime body test, and regenerated snapshots.

ℹ️ Other method enumerations still omit query

Two hard-coded HTTP-method lists were not extended, so QUERY operations are invisible to those code paths even though the shared httpMethods now includes them.

# Hard-coded method lists missing `query`

## Affected sites
- `packages/shared/src/openApi/shared/utils/patch.ts:62` and `:166` — the bulk `patch.operations` callback iterates `['get','put','post','delete','options','head','patch','trace']`; a `QUERY` operation is silently skipped, so user patch functions never see it (the record-based branch at `:79`/`:183` does work via `key.split(' ')`).
- `packages/json-schema-ref-parser/src/index.ts:551` — `HTTP_METHODS` set omits `query`, so when merging multi-file specs a `QUERY` method conflict on the same path is not detected and the operation can be overwritten instead of namespaced.

## Required outcome
- `query` should be handled consistently in both utilities, matching the new shared `httpMethods` list.

## Suggested approach (optional)
- Derive these lists from `httpMethods` (uppercasing for the parser set) rather than duplicating literals to avoid the same drift later.

ℹ️ Nitpicks

• packages/openapi-ts-tests/main/test/3.2.x.test.ts reimplements a simplified createConfig that diverges from the helper in 3.0.x.test.ts/3.1.x.test.ts (no array input/output handling, no nameConflictResolver passthrough), and only one scenario is covered. Worth aligning before the 3.2 suite grows.
• packages/openapi-ts/src/plugins/@hey-api/client-nuxt/bundle/client.ts:150 — method: opts.method as any is spread after ...asyncDataOptions, so it now always wins over a method supplied through asyncDataOptions (previously the latter won). This is likely intentional for QUERY typing, but it is a behavior change for direct request() calls where opts.method is undefined.

  ^{｜ Fix all ➔ ｜ Fix 👍s ➔ ｜ View workflow run ｜ Using deepseek-v4.1-flash (free via Pullfrog for OSS) ｜ 𝕏}