fix: Ignore additional tags added for VPC and subnets outside the module.

[gohmc]

Description

Currently, additional tags added to VPC and subnet resources outside the module will be remove when re-apply, even there's no change to the network topology. To prevent tags from removal unexpectedly, this PR added lifecycle ignore_changes to tags for resource aws_vpc and aws_subnet.

Steps to reproduce the behavior:

• Applied any of the example
• Manually add tags to the VPC and subnets created by this module. This simulate an external process (eg. INFOSEC) adding additional tags.
• Re-apply the same example and will see terraform plan to remove additional tags added outside the module.

Motivation and Context

Additional tags can be added post applied.

Breaking Changes

No.

How Has This Been Tested?

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

[antonbabenko]

This will not make it into the module because we want users to be able to manage tags across resources created by this module.

Closes #986

[github-actions[bot]]

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.