Fix protocol dependencies for smithy-rpc-v2-cbor when creating new service module

[alextwoods]

Fix protocol dependencies for smithy-rpc-v2-cbor when creating new service module

Motivation and Context

When new modules are created for rpcv2 cbor services we are currently incorrectly specifing the protocol dependency in the pom.xml, example error:

 Could not resolve dependencies for project software.amazon.awssdk:XXXXXXX:jar:2.32.3-SNAPSHOT: Could not find artifact software.amazon.awssdk:aws-smithy-rpc-v2-cbor-protocol:jar:2.32.3-SNAPSHOT

This is because the protocol name used in transformSpecialProtocols for rpcv2 is incorrect. The correct value for the protocol from c2j files is smithy-rpc-v2-cbor.

Modifications

• Update the protocol name to match that value from the c2j model: smithy-rpc-v2-cbor. This will now result in the correct protocol dependency: software.amazon.awssdk:smithy-rpcv2-protocol

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

[alextwoods]

Surface area API review is incorrectly flagging this as a change to a public/protected API - this is a change to only the constant used for substitution of protocol dependencies when creating new service modules.

[sonarqubecloud]

Quality Gate failed

Failed conditions
50.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.