fix: outputs for VPC and Subnets support new or existing

[toddgiguere]

Description

Fixed issues with certain output variables that did not support the new feature of using existing subnets. All outputs that are VPC or Subnet related should now be populated correctly depending on new or existing resources used.

Release required?

• No release
• Patch release (x.x.X)
• Minor release (x.X.x)
• Major release (X.x.x)

Release notes content

VPC and Subnet outputs should now support both new and existing resource definitions.

Run the pipeline

If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.

Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:

/run pipeline

Checklist for reviewers

• If relevant, a test for the change is included or updated with this PR.
• If relevant, documentation for the change is included or updated with this PR.

For mergers

• Use a conventional commit message to set the release level. Follow the guidelines.
• Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
• Use the Squash and merge option.

[toddgiguere]

/run pipeline

[ocofaigh]

/run pipeline

[terraform-ibm-modules-ops]

🎉 This PR is included in version 7.13.2 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀