Misc changes to useMutation types/docblocks:

- Fix promise result in pseudo-types on docs
- Fix wording for 'abort' method docblock

Author: Shrugsy

query-old/docs/api/created-api/hooks.md

@@ -95,7 +95,7 @@ type UseMutation<Definition> = () => [UseMutationTrigger<Definition>, UseMutatio
 
 type UseMutationTrigger<Definition> = (
   arg: ArgTypeFrom<Definition>
-) => Promise<{ data: ResultTypeFrom<Definition> }> & {
+) => Promise<{ data: ResultTypeFrom<Definition> } | { error: BaseQueryError | SerializedError }> & {
   arg: {
     endpointName: string; // The name of the given endpoint for the mutation
     originalArgs: ArgTypeFrom<Definition>; // Arguments passed to the mutation

src/query/core/buildInitiate.ts

@@ -121,7 +121,8 @@ export type MutationActionCreatorResult<
    * A method to cancel the mutation promise. Note that this is not intended to prevent the mutation
    * that was fired off from reaching the server, but only to assist in handling the response.
    *
-   * Calling `abort()` prior to the promise resolving will make it throw with an error like:
+   * Calling `abort()` prior to the promise resolving will force it to reach the error state with
+   * the serialized error:
    * `{ name: 'AbortError', message: 'Aborted' }`
    *
    * @example

src/query/tests/buildHooks.test.tsx

@@ -829,7 +829,6 @@ describe('hooks tests', () => {
 
           // no-op simply for clearer type assertions
           res.then((result) => {
-            // currently passing with a false positive, because error is getting typed as `any`
             expectExactType<
               | {
                   error: { status: number; data: unknown } | SerializedError