Change config for Sigv4a signing to not perform path normalization

[cenedhryn]

Motivation and Context

When the Sigv4a signer is used, path normalization is true by default. This causes issues for S3 MRAP usage, where some paths don't work - S3 does not perform path normalization

Modifications

This bugfix checks the signer attribute to see if it has a value, and chooses that value if it exists. Otherwise, it will fall back to true, which is the general Sigv4 setting. S3 and S3 Control always sets the path normalization to false.

Testing

No unit testing is possible because the normalization is performed in CRT, not in the SDK

Edit: added the path tests to existing integ tests

Screenshots (if appropriate)

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)

Checklist

• I have read the CONTRIBUTING document
• Local run of mvn install succeeds
• My code follows the code style of this project
• My change requires a change to the Javadoc documentation
• I have updated the Javadoc documentation accordingly
• I have added tests to cover my changes
• All new and existing tests passed
• I have added a changelog entry. Adding a new entry must be accomplished by running the scripts/new-change script and following the instructions. Commit the new file created by the script in .changes/next-release with your changes.
• My change is to implement 1.11 parity feature and I have updated LaunchChangelog

License

• I confirm that this pull request can be released under the Apache 2 license

[sonarqubecloud]

SonarCloud Quality Gate failed.   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

0.0% Coverage
0.0% Duplication

Catch issues before they fail your Quality Gate with our IDE extension SonarLint