jersey-netty-connector - Content-Length and Host header should not be set if they are present in the jersey request

When using HTTP Authorization header of type Signature, the headers used to compute the signature is set in the headers map that is part of the jersey request. jersey-netty-connector should not be setting the headers that is already present in the jersey request.

Example -
Authorization: Signature keyId="ocid1***",algorithm="rsa-sha256",headers="date (request-target) host content-length content-type x-content-sha256",signature="EfdJhBrpwJW8M*****",x-content-sha256: 47DEQpj8HBSa+*******

In this case Host header should not be added and Content-Length header should be preserved