Fix dependency generation for new smithy-rpc-v2-cbor services

[alextwoods]

Fix dependency generation for new smithy-rpc-v2-cbor services

Motivation and Context

Generation of new smithy-rpc-v2-cbor services is failing with:

[WARNING] Used undeclared dependencies found:
[WARNING]    software.amazon.awssdk:aws-json-protocol:jar:2.32.4-SNAPSHOT:compile

org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:3.1.1:analyze-only (default) on project arcregionswitch: Dependency problems found

While the aws-cbor-protocol module does define a dependency on aws-json-protocol, the code generation also generates code into the service module that has direct dependencies on aws-json-protocol, causing the undeclared dependencies issue above.

Modifications

• Adds a static map of additional dependencies per protocol that are added to the list.

Testing

Manual testing

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]

Quality Gate failed

Failed conditions
60.0% Coverage on New Code (required ≥ 80%)

See analysis details on SonarQube Cloud

[github-actions]

This pull request has been closed and the conversation has been locked. Comments on closed PRs are hard for our team to see. If you need more assistance, please open a new issue that references this one.