Adjustments to JerseyClientBuilder to use configuration options otherwise ignored

Please see issue #557 in the issue tracker.

The basic problem was that the DW JerseyClientBuilder didn't properly take into account a lot of the configuration options you can pass to a Client object, particularly the proxying features.  This uses code taken from ApacheHttpClient4 to process those configuration options and get them into the ClientHandler object so they'll be properly picked up.

This is my first pull request, so apologies if I did it wrong.  :)
I'm happy to help but I'm not sure what you mean - I haven't really used
Github much, so sorry if I sound kind of dumb here.  The changes are pushed
to the branch tied to the pull request as I understand it; I'm not sure
what it is about the pull request I need to update.  Just let me know
exactly what it is you need and I'll get it done.

Thanks, Patrick

On Sun, Nov 9, 2014 at 8:38 AM, Jochen Schalanda <notifications@github.com>
wrote:

> In
> dropwizard-client/src/main/java/io/dropwizard/client/JerseyClientBuilder.java:
>
> >  import java.util.List;
> >  import java.util.Map;
> >  import java.util.concurrent.ExecutorService;
> > +import java.util.logging.Level;
> > +import java.util.logging.Logger;
>
> Would you mind updating this PR with the changes you've made? Thanks!
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/dropwizard/dropwizard/pull/558/files#r20058721>.
>