We should provide adapters for building all HttpClient variants

Today we only have `StreamingHttpClientAdapter` which facilitates creation of `StreamingHttpClient` filters given it helps with providing the `StreamingHttpRequestResponseFactory` and delegating all method calls.
We don't have the equivalent adapter for the other programming models to allow users to create filters at that API layer. For example users at the `BlockingHttpClient` API layer can't create a `BlockingHttpClient` filter, they are forced to write a filter using the `StreamingHttpClient` API.

Start by locating the existing StreamingHttpClientAdapter and trace how it supplies the StreamingHttpRequestResponseFactory and delegates method calls. Identify the other HttpClient programming models that need equivalent adapters, then verify each API layer can create filters without dropping to the streaming API.

Written by the indexing model from the issue text.