feat: Support multiple tgw route tables (v2)

[flah00]

Description

Based on issues#139, attempt to add support for multiple route tables for a single tgw.

Of course we're all looking forward to #113. But just in case its release is not imminent.. This could tide us over?

Motivation and Context

issues#139

Breaking Changes

Additive, it's a new module

How Has This Been Tested?

• I have updated at least one of the examples/* to demonstrate and validate my change(s)
• I have tested and validated these changes using one or more of the provided examples/* projects

• I have executed pre-commit run -a on my pull request

[flah00]

@antonbabenko @bryantbiggs bump :)

[bryantbiggs]

I don't think we'll be proceeding with this one - it doesn't make a lot of sense to add a temporary sub-module to unblock this. if this is a suitable solution for the interim, users can implement it on their own - we don't want to take on the burden of trying to migrate users off this at a later date

[flah00]

Fair enough
Is there anything we can do to help get v3 over the line?

[github-actions]

This PR has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this PR will be closed in 10 days

[github-actions]

This PR was automatically closed because of stale in 10 days

[github-actions]

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.