jersey-netty-connector ER - need the ability to set the headers required for redirection

[sxsubram]

As part of #5414 certain http headers were dropped during redirection to be spec compliant. We have a use case where request is routed from runtime component to the designtime component within the same domain. This use case is broken with the removal of the http auth headers. We have product use cases that require the auth headers and customer use case that require the auth header to be stripped.
To be able to support both use cases, we need the ability to set the headers used for redirection based on context. I am filing this ER for jersey-netty-connector to provide a redirectionResponseInterceptor so implementers can determine the headers that can set/dropped. The interceptor would need to provide access to the response headers and the original request and use the returned list of headers in the redirected request.