WebTransport integration on top of the webtransport library.

A handler that wants to accept a WebTransport session (initiated by an HTTP extended CONNECT with :protocol = webtransport) calls upgrade/3. The function dispatches to the adapter's accept_wt/4 helper, which reconstructs the CONNECT pseudo-headers and calls webtransport:accept/4. On success the stream/session belongs to the webtransport session process and upgrade/3 returns the taken_over sentinel response.

my_wt_route(Req) ->
    livery_wt:upgrade(Req, my_wt_handler, #{}).

my_wt_handler implements the webtransport_handler behaviour (from erlang-webtransport).

WebTransport runs only over H2 (extended CONNECT, RFC 9220-style) and H3. Calling upgrade/3 on H1 returns 501 Not Implemented.

The listener must advertise the WebTransport settings. Merge webtransport:h3_settings/0 (or h2_settings/0) into the listener options so the adapter forwards the H3/H2 SETTINGS, datagram support, and WT stream routing to the wire library:

Opts = maps:merge(webtransport:h3_settings(), #{
    cert => Cert, key => Key, stack => Stack,
    handler => fun(Req) -> livery_wt:upgrade(Req, my_handler, #{}) end
}),
livery_h3:start(Opts).

End-to-end bidi-stream and datagram echo over a real session is covered by livery_wt_SUITE (needs webtransport >= 0.2.3, where accept/4 works from Livery's per-request worker process).