Specify aws-core -> http-auth-aws as test dependency

[gosar]

Motivation and Context

In the PR to switch S3 to SRA, aws-core -> http-auth-aws dependency was added here but it only needs to be a test dependency because of this change

It is safe to remove this explicit dependency from aws-core -> http-auth-aws. It is still being transitively brought it via aws-core -> sdk-core -> http-auth-aws, so it shouldn't affect customers specifying a dependency on aws-core but using classes from http-auth-aws without declaring explicit dependency.

Modifications

Made the dependency only test scope.

Testing

./mvnw clean install -pl :aws-core passes locally.

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

[sonarcloud]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud