[Feature]: Generate V3 client name and package name according to v3 release

[AllanZhengYP]

Self-service

• I'd be willing to implement this feature

Description

Currently the V3 package names are static: code, but the upstream V3 SDK repo releases new clients constantly. This is not scalable for maintainers to update this list often.

We can create a workflow to add new package/client names to the metadata automatically, either by periodically checking the V3 repo or triggered by a V3 GitHub release.

[trivikr]

Looking at the frequency of additional services being added, and the exceptions between v2 and v3 client names, I think manual updates to clients would require less work.

If we're planning to add a workflow, this is where client names are decided from:

• v2: https://github.com/aws/aws-sdk-js/blob/d05708ee0b52974be66b185410fde1900ee9a1c0/lib/model/api.js#L41-L48
• v3: https://github.com/awslabs/smithy-typescript/blob/90eac3249d5576f0dd28b4a84e5744877d93f94a/smithy-typescript-codegen/src/main/java/software/amazon/smithy/typescript/codegen/CodegenVisitor.java#L421

The exception will need to be added in CLIENT_NAMES_MAP.ts only if there's a difference between naming in v2 and v3.

[trivikr]

A semi-automation was added in #204 to generate new-client tests from enums. The names need to be verified manually though.

And example update for clients can be viewed at #201

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.