[3.9] bpo-45772: socket.socket should be a class instead of a function (GH-23960) (GH-29543)

* [bpo-45772](): socket.socket should be a class instead of a function

Currently `socket.socket` is documented as a function, but it is really
a class (and thus has function-like usage to construct an object). This
correction would ensure that Python projects that are interlinking
Python's documentation can properly locate `socket.socket` as a type.
(cherry picked from commit 4c792f3)


Co-authored-by: Hong Xu <[email protected]>

Automerge-Triggered-By: GH:asvetlov

Author: miss-islington

Doc/library/socket.rst

@@ -552,7 +552,7 @@ Creating sockets
 The following functions all create :ref:`socket objects <socket-objects>`.
 
 
-.. function:: socket(family=AF_INET, type=SOCK_STREAM, proto=0, fileno=None)
+.. class:: socket(family=AF_INET, type=SOCK_STREAM, proto=0, fileno=None)
 
    Create a new socket using the given address family, socket type and protocol
    number.  The address family should be :const:`AF_INET` (the default),

Misc/NEWS.d/next/Documentation/2021-11-09-13-10-55.bpo-45772.EdrM3t.rst

@@ -0,0 +1 @@
+``socket.socket`` documentation is corrected to a class from a function.