Implement wait logic in transite gateway attachment

[hongil0316]

Description

Fixes #624.

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 / Removed / Updated [X].

Migration Guide

[yhakbar]

Why not use a waiter, @hongil0316 ?

[hongil0316]

Why not use a waiter, @hongil0316 ?

I wasn't actually aware of this approach. However, currently most of the resources are using SDK v1 and the wait logic is implemented similar to the change being implemented here. If we want to introduce this, I think we should do it in a separate PR with bigger plan for consistency across the code base.