Urllib3-future

=====================

- Fixed dangling task waiting for timeout when using Happy Eyeballs in a synchronous context.

=====================

- Fixed thread/task safety with WebSocket R/W operations.
- Fixed missing propagation of callbacks (e.g. ``on_post_connection``) in retries of failed requests.

=====================

- Fixed exception leaks in ExtensionFromHTTP plugins. Now every extension behave and raise urllib3 own exceptions.
- Added automatic connection downgrade HTTP/2 -> HTTP/1.1 or HTTP/3 -> (HTTP/2 or HTTP/1.1) in case of known recoverable issues.
- Fixed a rare issue where the write semaphore (async context) for a datagram socket would be locked forever in case of an error.

=====================

- Fixed call to ``stream(..)`` on (early) informational responses. The inner ``fp`` was set to ``None`` and the function
``is_fp_closed`` is not meant to handle this case. Through you should never expect a body in those responses.
- Fixed ``read()``, and ``data`` returns None for (early) informational responses.

=====================

- Fixed closed state on a WebSocketExtensionFromHTTP when the remote send a CloseConnection event.
- Fixed an edge case where a DNS-over-HTTPS would start of a non-multiplexed connection but immediately upgrade to a
multiplexed capable connection would induce an error.
- Allow to disable HTTP/1.1 in a DNS-over-HTTPS resolver.
- Extra "qh3" lower bound aligned with the main constraint ``>=1.2,<2``.

=====================

- Added complete support for Informational Response whether it's an early response or not. We introduced a callback named
``on_early_response`` that takes exactly one parameter, namely a ``HTTPResponse``. You may start leveraging Early Hints!
This works regardless of the negotiated protocol: HTTP/1.1, HTTP/2 or HTTP/3! As always, you may use that feature
in a synchronous or asynchronous context.
- Changed ``qh3`` lower bound version to v1.2 in order to support Informational Response in HTTP/3 also.
- Added full automated support for WebSocket through HTTP/1.1, HTTP/2 or HTTP/3.
In order to leverage this feature, urllib3-future now recognize url scheme ``ws://`` (insecure) and ``wss://`` (secure).
The response will be of status 101 (Switching Protocol) and the body will be None.
Most servers out there only support WebSocket through HTTP/1.1, and using HTTP/2 or HTTP/3 usually ends up in stream (reset) error.
By default, connecting to ``wss://`` or ``ws://`` use HTTP/1.1, but if you desire to leverage the WebSocket through a multiplexed connection,
use ``wss+rfc8441://`` or ``ws+rfc8441://``.
A new property has been introduced in ``HTTPResponse``, namely ``extension`` to be able to interact with the websocket
server. Everything is handled automatically, from thread safety to all the protocol logic. See the documentation for more.
This will require the installation of an optional dependency ``wsproto``, to do so, please install urllib3-future with
``pip install urllib3-future[ws]``.
- Fixed a rare issue where the ``:authority`` (special header) value might be malformed.