Import upstream CPython 3.14 (rc1 release!)

Summary:
Python `3.14.0rc1+` was released on 2025-07-22 18:54:14+00:00.
Base: (`3.14.0b4+`) - `c59a60bdb48120fe7b7ba65507448db358b6671d` (release date: 2025-07-22 10:32:00+00:00)
Imported: (`3.14.0rc1+`) - `9f25781bf9b4e14cdc7a165a6bc1c15cf7d736e5` (release date: 2025-07-22 18:54:14+00:00)

# Files added

```
Misc/NEWS.d/3.14.0rc1.rst
Tools/wasm/emscripten/wasm_assets.py
Tools/wasm/emscripten/web_example/index.html
Tools/wasm/emscripten/web_example_pyrepl_jspi/index.html
Tools/wasm/emscripten/web_example_pyrepl_jspi/src.mjs
```

# Files removed

https://www.internalfb.com/intern/everpaste/?color=0&handle=GA59Gh-xhwDEqWwOAMvLWveSDHIJbr0LAAAz

Reviewed By: bowiechen

Differential Revision: D78804514

fbshipit-source-id: dc132d00e896008168843b148547b02e3424a3e7

Author: itamaro

Doc/c-api/arg.rst

@@ -113,18 +113,14 @@ There are three ways strings and buffers can be converted to C:
 ``z`` (:class:`str` or ``None``) [const char \*]
    Like ``s``, but the Python object may also be ``None``, in which case the C
    pointer is set to ``NULL``.
-   It is the same as ``s?`` with the C pointer was initialized to ``NULL``.
 
 ``z*`` (:class:`str`, :term:`bytes-like object` or ``None``) [Py_buffer]
    Like ``s*``, but the Python object may also be ``None``, in which case the
    ``buf`` member of the :c:type:`Py_buffer` structure is set to ``NULL``.
-   It is the same as ``s*?`` with the ``buf`` member of the :c:type:`Py_buffer`
-   structure was initialized to ``NULL``.
 
 ``z#`` (:class:`str`, read-only :term:`bytes-like object` or ``None``) [const char \*, :c:type:`Py_ssize_t`]
    Like ``s#``, but the Python object may also be ``None``, in which case the C
    pointer is set to ``NULL``.
-   It is the same as ``s#?`` with the C pointer was initialized to ``NULL``.
 
 ``y`` (read-only :term:`bytes-like object`) [const char \*]
    This format converts a bytes-like object to a C pointer to a
@@ -387,17 +383,6 @@ Other objects
       Non-tuple sequences are deprecated if *items* contains format units
       which store a borrowed buffer or a borrowed reference.
 
-``unit?`` (anything or ``None``) [*matching-variable(s)*]
-   ``?`` modifies the behavior of the preceding format unit.
-   The C variable(s) corresponding to that parameter should be initialized
-   to their default value --- when the argument is ``None``,
-   :c:func:`PyArg_ParseTuple` does not touch the contents of the corresponding
-   C variable(s).
-   If the argument is not ``None``, it is parsed according to the specified
-   format unit.
-
-   .. versionadded:: 3.14
-
 A few other characters have a meaning in a format string.  These may not occur
 inside nested parentheses.  They are:
 

Doc/library/annotationlib.rst

@@ -511,7 +511,7 @@ code execution even with no access to any globals or builtins. For example:
 
   >>> def f(x: (1).__class__.__base__.__subclasses__()[-1].__init__.__builtins__["print"]("Hello world")): pass
   ...
-  >>> annotationlib.get_annotations(f, format=annotationlib.Format.SOURCE)
+  >>> annotationlib.get_annotations(f, format=annotationlib.Format.STRING)
   Hello world
   {'x': 'None'}