Use RedirectStrategy from HttpClient rather than a custom approach

We have a custom implementation where we follow relocations for status codes 3xx. We can leverage RedirectStrategy implementations instead doing this on our own.

WAGON-568 revealed a very serious bug in our codebase. We blindly assume that requests can always be retried, regardless whether the HttpEntity is repeatable or not. This can lead to a lockup of the transport because we advertise a content length on input streams, but cannot deliver those bytes. It will block until the server sends a 408.