Fix Sigv4a-signed requests to endpoints with non-standard ports.

[millems]

The signed host header must match the host header sent on the wire. HTTP clients append the port to the host header if the port is non-standard for the protocol being used. The current Sigv4a signer only adds the host, not the port, to the host header. This means that endpoints with non-standard ports for the protocol (e.g. an HTTPS service on port 8443) would get a signature validation failure, because the HTTP client will change the host header.

The Sigv4 signer handles this by adding the host header and port before calculating the signature. This PR adds that same logic to the Sigv4a signer.

[sonarqubecloud]

SonarCloud Quality Gate failed.   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
1 Code Smell

0.0% Coverage
0.0% Duplication