fix: type useQuery's data from select, as TanStack does

[julien1619]

Problem

The generated useQuery typed its options as Omit<UseQueryOptions, 'queryKey' | 'queryFn'>. UseQueryOptions is a MaybeRef<…>, and Omit over that union keeps no key, so:

• select received an implicit any;
• data stayed typed as the raw payload, whatever select returned.

Change

• useQuery is generic in TData (default: the endpoint's data). Its options are the plain variant of UseQueryOptions<_QD, DefaultError, TData, _QD, QueryKey>, so TanStack infers TData from select exactly like its own useQuery. A select expecting another input than the payload is refused.
• fetchQuery / ensureQueryData get FetchQueryOptions / EnsureQueryDataOptions on the endpoint's data (no select, as neither applies one).
• Every GET method goes through a single _get fetch; _QD is its resolved type, with or without an output schema.
• enabled and queryKey behave as before.

Tests

playground/app.vue pins the types (checked by npm run test:types):

• no select → data is the payload, not any;
• select → data is the selected type, not any;
• a select with a wrong input type → error;
• an endpoint without options infers the same way.

Against the previous generator, these checks fail with 4 errors. CI now runs test:types, which previously ran only locally.

Verified on a consumer app (Mesalia booking): replacing a hand-rolled TanStack query by the generated useQuery(o, { select }) typechecks with the selected types.

🤖 Generated with Claude Code