Remove socket prewarming

The potential for breakage is too high, and I am working on an
alternative solution that will be better long term.

Prewarming is still used for kittens launched via keybindings

docs/build.rst

@@ -23,10 +23,6 @@ following dependencies are installed first.
    should use a version of the source that matches the binary version as closely
    as possible, since the two are tightly coupled.
 
-   You may need to unset the :envvar:`KITTY_PREWARM_SOCKET` environment variable,
-   otherwise your modified code will not be executed, when running some of the
-   ``kitty +`` and ``kitty @`` commands.
-
 
 Dependencies
 ----------------

docs/changelog.rst

@@ -40,7 +40,7 @@ Detailed list of changes
 
 - A new option :opt:`remote_control_password` to use fine grained permissions for what can be remote controlled (:disc:`5320`)
 
-- Reduce startup latency by ~30 milliseconds when running kittens and remote control commands inside kitty (:iss:`5159`)
+- Reduce startup latency by ~30 milliseconds when running kittens via key bindings inside kitty (:iss:`5159`)
 
 - A new option :opt:`modify_font` to adjust various font metrics like underlines, cell sizes etc. (:pull:`5265`)
 

docs/glossary.rst

@@ -142,17 +142,6 @@ Variables that kitty sets when running child programs
    A public key that programs can use to communicate securely with kitty using
    the remote control protocol. The format is: :code:`protocol:key data`.
 
-.. envvar:: KITTY_PREWARM_SOCKET
-
-   Path to a UNIX domain socket used to avoid Python interpreter startup
-   latency when running kittens, or remote control or using ``kitty +launch`` or
-   ``kitty +runpy``.
-
-.. envvar:: KITTY_PREWARM_SOCKET_REAL_TTY
-
-   Path to the the PTY used to run the prewarmed process in when using
-   :envvar:`KITTY_PREWARM_SOCKET`.
-
 .. envvar:: WINDOWID
 
    The id for the :term:`OS Window <os_window>` the program is running in. Only available