Code examples: update validation list and IDs of enhanced actions

[Laren-AWS]

Description

• Add entry to allow list to pass validation.
• Use the sdk_action name instead of the underlying REST API action name to form the example ID and service.action entry for enhanced actions. An enhanced action is one that adds additional features to an underlying client action.

Motivation and Context

The enhanced action change is needed to avoid multiple examples with the same ID. Because the ID is used as a key to merge examples, multiple examples with the same ID meant that they were overwriting each other. By using the SDK-specific action name in both the ID and the services.action list, they are each treated as individual actions.

Testing

• Ran the -tools validator and everything passes.
• Built and internal cloud desktop build.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist

We require a second engineer to validate the PR before merging

• My code builds in Gamma and passes backward compatibility validation (required)
• My code follows the code style of this project
• My change requires a change to the documentation
• I have updated the documentation accordingly
• I have read the README document
• I have added tests to cover my changes
• All new and existing tests passed

New/existing dependencies impact assessment, if applicable

Note to reviewers: Please follow runbook to update the internal open source attribution tool

License

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

[jnunn-aws]

Merging to private repo: https://github.com/aws/PRIVATE-aws-tools-for-powershell-staging/pull/323

[jnunn-aws]

This has been merged.