Add HttpClient as a better name than HttpClientContext with deprecation

[rbygrave]

I have convinced myself that HttpClient is a better name than HttpClientContext. This does mean that it has the same short name as the underlying java.net.http.HttpClient but I think that is ok as:

1. We generally don't need to supply JDK HttpClient but instead just it's builder options (so we very rarely hit the short name collision)
2. Other projects use HttpClient as their name.

To me it's become really clear that HttpClientContext is a pretty bad name so going for this change. This includes deprecation of HttpClientContext.builder() in favor of HttpClient.builder(). We will keep both for some time to allow people to migrate.

[SentryMan]

Can we perhaps also change the HttpApiProvider interface to use the new superclass? I tried changing the http-client-generator, but got errors.

[rbygrave]

I tried changing the http-client-generator, but got errors.

I need to merge this and release this client and then it will work.

also change the HttpApiProvider interface to use the new superclass?

We don't need to immediately as HttpClientContext extends HttpClient so both are expected to work with the generated code as it is (it should support existing client generated code) ... but yes I see that PR and yes we can merge that in once this is released.

[SentryMan]

I need to merge this and release this client and then it will work.

I mean I had these changes on my local repository and it still doesn't generate

[SentryMan]

hmm, I guess I was wrong, it does work