See gh-26041

Closes gh-6719

Closes gh-26051

Closes gh-26077

Closes gh-26076

Closes gh-26075

Apache HttpClient 5.1 doesn't cope with Jetty 10 sending
SETTINGS_ENABLE_CONNECT_PROTOCOL in the settings frame. It also appears
to be unstable when using Undertow, resulting in a failure and
"UT005032: Listener not making progress on framed channel, closing
channel to prevent infinite loop" being logged on the server-side.

Local experimentation suggests that Jetty's HTTP/2 client is more
robust and that it does not trigger the problem with Undertow. It also
fixes the problem with SETTINGS_ENABLE_CONNECT_PROTOCOL when testing
against Jetty 10 so this commit updates the tests to use Jetty's client.

Closes gh-26040

Closes gh-26073

Closes gh-26072

Closes gh-26071

Closes gh-26070

Closes gh-26069

Closes gh-26068

Closes gh-26067

Closes gh-26066

Closes gh-26065

Closes gh-26064

Closes gh-26063

Closes gh-26062

Closes gh-26061

Closes gh-26060

Closes gh-26059

Closes gh-26058

Closes gh-26057

Closes gh-26056

Closes gh-26055

Closes gh-26054

Closes gh-26052

Closes gh-26050

Closes gh-26049

Closes gh-26048

Closes gh-26047

Closes gh-26046

Closes gh-26045

Closes gh-26044

Closes gh-26043

Closes gh-25926

Closes gh-25909