Jetty HttpClient in HTTP/1.1 mode, using Blocking APIs, will not idle timeout when encountering unexpected 1xx (Informational) status codes.

```
[HTTP/1.1 104 Upload Resumption Supported
Upload-Offset: 50

HTTP/1.1 200 OK
Content-Type: text/plain
Content-Length: 13

Hello, world.
```

Test cases in https://github.com/greenbytes/java-http-1xx-tests; run

`mvn clean install -Dtest=JettyHttpClientTests#testJettyHttpClient104_1`

Note that the problem is the same for any informational status code >= 103.

Run `mvn clean install -Dtest=JettyHttpClientTests#testJettyHttpClient104_1` and use the linked java-http-1xx-tests cases to reproduce the blocking HTTP/1.1 client behavior. Trace how Jetty HttpClient handles unexpected informational responses at or above 103; done means the client observes the idle timeout instead of waiting indefinitely.

Written by the indexing model from the issue text.