Update AWS force destroy script, include lingering volumes

[iameskild]

Reference Issues or PRs

As part of the work to fix the integration tests, we need to make sure that all the cloud resources are always destroyed. AWS has consistently been the trickiest cloud provider in this regard. This is because individual resources need to be manually deleted if anything with nebari destroy goes wrong.

I am continuing the work I started a few weeks ago and cleaning up this script, most notably ensuring that any lingering volumes are also destroyed.

What does this implement/fix?

Put a x in the boxes that apply

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds a feature)
• Breaking change (fix or feature that would cause existing features not to work as expected)
• Documentation Update
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no API changes)
• Build related changes
• Other (please describe): clean up script

Testing

• Did you test the pull request locally?
• Did you add new tests?

Any other comments?