fix: make aws promote quarantine template support multiple subnets

[JimLin94]

fix: make aws promote quarantine template support multiple subnets

Change Summary

Purpose:

Align the VPC config with the stack template to support connecting multiple subnets with the promote quarantine plugin.

Verify the solution:

Deploy the promote /quarantine plugin with two subnet IDs and two security group ids.

Deploy the promote /quarantine plugin with one subnet ID and one security group ID.

Deploy the promote /quarantine plugin with only one subnet ID, and it should not be enabled the VPC

Deploy the promote /quarantine plugin with only one security group ID, and it should not be enabled the VPC

PR Checklist

• [x] I've read and followed the Contributing Guide.
• Documents/Readmes
  • [ ] Updated accordingly
  • [x] Not required
• Plugins that have versioning
  • [x] Version bumped and follows Semantic Versioning
  • [ ] (Azure Only): Ensure the version for the package location in template.json has been updated
  • [ ] Not required

Other Notes