docs: match the error-message examples to what the parsers emit

The "Handling errors" examples dropped the ", received X" suffix that
invalid_type messages have always carried; the strings were never correct.

The Zod Mini tab needed a different value: @zod/mini ships without the en
locale, so its messages stay at a bare "Invalid input" until the consumer
calls z.config(z.locales.en()).

Closes #6589

Author: colinhacks

packages/docs/content/basics.mdx

@@ -71,13 +71,13 @@ try {
         expected: 'string',
         code: 'invalid_type',
         path: [ 'username' ],
-        message: 'Invalid input: expected string'
+        message: 'Invalid input: expected string, received number'
       },
       {
         expected: 'number',
         code: 'invalid_type',
         path: [ 'xp' ],
-        message: 'Invalid input: expected number'
+        message: 'Invalid input: expected number, received string'
       }
     ] */
   }
@@ -96,13 +96,13 @@ try {
         expected: 'string',
         code: 'invalid_type',
         path: [ 'username' ],
-        message: 'Invalid input: expected string'
+        message: 'Invalid input'
       },
       {
         expected: 'number',
         code: 'invalid_type',
         path: [ 'xp' ],
-        message: 'Invalid input: expected number'
+        message: 'Invalid input'
       }
     ] */
   }

packages/zod/README.md

@@ -155,13 +155,13 @@ try {
         expected: 'string',
         code: 'invalid_type',
         path: [ 'username' ],
-        message: 'Invalid input: expected string'
+        message: 'Invalid input: expected string, received number'
       },
       {
         expected: 'number',
         code: 'invalid_type',
         path: [ 'xp' ],
-        message: 'Invalid input: expected number'
+        message: 'Invalid input: expected number, received string'
       }
     ] */
   }