register missing resource - TGW Peering Attachment

[wakeful]

Description

I was running dead code analysis and noticed that the TransitGatewayPeeringAttachment resource is not being used.

aws/resources/tgw_peering_attachment.go:14:46: unreachable func: TransitGatewayPeeringAttachment.getAll
aws/resources/tgw_peering_attachment.go:34:46: unreachable func: TransitGatewayPeeringAttachment.nukeAll
aws/resources/tgw_peering_attachment_types.go:22:46: unreachable func: TransitGatewayPeeringAttachment.Init
aws/resources/tgw_peering_attachment_types.go:26:46: unreachable func: TransitGatewayPeeringAttachment.ResourceName
aws/resources/tgw_peering_attachment_types.go:30:46: unreachable func: TransitGatewayPeeringAttachment.MaxBatchSize
aws/resources/tgw_peering_attachment_types.go:34:46: unreachable func: TransitGatewayPeeringAttachment.ResourceIdentifiers
aws/resources/tgw_peering_attachment_types.go:38:46: unreachable func: TransitGatewayPeeringAttachment.GetAndSetResourceConfig
aws/resources/tgw_peering_attachment_types.go:42:46: unreachable func: TransitGatewayPeeringAttachment.GetAndSetIdentifiers
aws/resources/tgw_peering_attachment_types.go:52:46: unreachable func: TransitGatewayPeeringAttachment.Nuke

TODOs

Read the Gruntwork contribution guidelines.

• Update the docs.
• Run the relevant tests successfully, including pre-commit checks.
• Ensure any 3rd party code adheres with our license policy or delete this line if its not applicable.
• Include release notes. If this PR is backward incompatible, include a migration guide.
• Attention Grunts - if this PR adds support for a new resource, ensure the nuke_sandbox and nuke_phxdevops jobs in .circleci/config.yml have been updated with appropriate exclusions (either directly in the job or via the .circleci/nuke_config.yml file) to prevent nuking IAM roles, groups, resources, etc that are important for the test accounts.

Release Notes (draft)

Added TransitGatewayPeeringAttachment to be loaded.

Migration Guide

n/a

[james03160927]

LGTM

[james03160927]

It seems like there are some merge conflict. We can submit it once it's resolved.

[wakeful]

It seems like there are some merge conflict. We can submit it once it's resolved.

resolved

[wakeful]

hey @james03160927

I added another commit to this MR with code changes to move the transit-gateway-peering-attachment resource to AWS SDK v2.

[james03160927]

LGTM