Add proper handling for redirects when using HTTP Upgrade

Two possibilities: -

1 - Provide a mechanism that allows a meaningful error message to be displayed to an end user so they can pick a more appropriate address.

2 - Provide some way to actually handle the redirect.

Overall this will most likely require passing back to the code calling XNIO rather than being silently handled within XNIO.

As an example the WildFly CLI has different Remoting providers registered the http and https, also different Options for establishing the connection - for this reason it may be better to allow some form of 'RedirectException' to be passed back up and allow the client code to decide how to handle it.