Fix dependency violation errors when deleting EC2 VPC resource types

[james03160927]

Description

Fixes #584.
However, some VPC requires to run the cloud-nuke operations twice to delete completely. Some of the errors I couldn't resolve with this change:

• ERROR Failed to nuke vpc with err: DependencyViolation: Network vpc-00db40ad268a8758a has some mapped public address(es). Please unmap those public address(es) before detaching the gateway.
• ERROR Failed to nuke vpc with err: DependencyViolation: The subnet 'subnet-0ba8f9c12269ecc6c' has dependencies and cannot be deleted.

The first error goes away when I run it the second time.
The second error seems to be legit error that subnet is being used in other instances. The caller would have to cleanup other resources (dependent) before nuking vpc.

TODOs

Read the Gruntwork contribution guidelines.

• Update the docs.
• Run the relevant tests successfully, including pre-commit checks.
• Ensure any 3rd party code adheres with our license policy or delete this line if its not applicable.
• Include release notes. If this PR is backward incompatible, include a migration guide.
• Attention Grunts - if this PR adds support for a new resource, ensure the nuke_sandbox and nuke_phxdevops jobs in .circleci/config.yml have been updated with appropriate exclusions (either directly in the job or via the .circleci/nuke_config.yml file) to prevent nuking IAM roles, groups, resources, etc that are important for the test accounts.

Release Notes (draft)

Added / Removed / Updated [X].

Migration Guide

[MoonMoon1919]

Small nit, otherwise lgtm