feat: New CloudWAN and Transit Gateway subnets

[wiseelf]

Description

Added two additional subnets for Transit Gateway and CloudWAN.

Motivation and Context

In order to follow AWS best practices for CloudWAN and Transit Gateway there is a need in two additional subnets for each. Example of documentation: https://docs.aws.amazon.com/vpc/latest/tgw/tgw-best-design-practices.html

Use a separate subnet for each transit gateway VPC attachment. For each subnet, use a small CIDR, for example /28, so that you have more addresses for EC2 resources. When you use a separate subnet, you can configure the following:

1. Keep the inbound and outbound network ACLs associated with the transit gateway subnets open.
2. Depending on your traffic flow, you can apply network ACLs to your workload subnets.

Breaking Changes

No breaking changes

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

[wiseelf]

@antonbabenko @bryantbiggs sorry for the mention, but please review, not sure how to assign reviewers here.

[sknmi]

We would like to have this as well. Also this fixes: #888