fix(query): pass enabled option into queryOptions mutator (#3389)

* fix(query): pass enabled option into queryOptions mutator

When `allParamsOptional` is combined with a custom `queryOptions` mutator,
the generated query options helper passed `{ ...queryOptions, queryKey,
queryFn }` to the mutator, dropping the `enabled` guard (and any override
options) that the non-mutator branch emits via `queryOptionsImp`.

The query then ran even while a required path param was nullish, hitting a
broken URL. Pass the same object shape the non-mutator branch returns so the
`enabled` guard reaches the mutator, and so `...queryOptions` stays last and
remains overridable.

Closes #1522

* test(query): match issue-1522 mutator call verbatim

The issue-1522 regression test sliced the generated `customQueryOptions(...)`
call by searching for the first `});`, which a nested call site in the
argument could truncate. Match the whole call verbatim instead — generation
is deterministic — and assert it appears once per query helper.

Author: wadakatu

packages/query/src/query-generator.ts

@@ -649,9 +649,12 @@ ${hookOptions}
 
       ${
         queryOptionsMutator
-          ? `const customOptions = ${
+          ? // Pass the same options object the non-mutator branch returns so
+            // generated guards (e.g. the `enabled` clause for nullish path
+            // params) reach the mutator instead of being dropped. See #1522.
+            `const customOptions = ${
               queryOptionsMutator.name
-            }({...queryOptions, queryKey, queryFn}${
+            }({ queryKey, queryFn, ${queryOptionsImp}}${
               queryOptionsMutator.hasSecondArg ? `, { ${queryProperties} }` : ''
             }${
               queryOptionsMutator.hasThirdArg ? `, { url: \`${route}\` }` : ''