fix(iot-thinggroups): support deleting dynamic thing groups

[ekristen]

Attempts to fix deleting dynamic thing groups which was brought up rebuy-de/aws-nuke#1199.

Creating dynamic thing groups are bit more complicated so this is tough to test.

[ekristen]

@rstalbow can you test one of the builds from the zip file located here? https://github.com/ekristen/aws-nuke/actions/runs/8291642110/artifacts/1328506343

This is my rewrite of aws-nuke that I've been working on. docs and reason for why the rewrite is here If you modify your configuration to target just IoTThingGroup then you can specifically test this without affecting anything else.

If you'd like to help test this version out, I would appreciate it, but if not, I understand.

This is an example configuration you can use, this makes use of the a feature from my fork that does dynamic region discovery, feel free to replace - all with your specific regions.

regions:
  - all

blocklist:
  - "123456789012"

accounts:
  "123456789012": {}

resource-types:
  includes:
    - IoTThingGroup

aws-nuke run --config example.yaml

You should see output similar to this.

> aws-nuke - 3.0.0-dev - dirty
Do you really want to nuke the account with the ID 123456789012 and the alias 'no-alias-123456789012'?
Waiting 3s before continuing.
us-east-1 - IoTThingGroup - test - [Name: "test", Type: "static"] - would remove
us-east-1 - IoTThingGroup - test1 - [Name: "test", Type: "dynamic"] - would remove
Scan complete: 2 total, 2 nukeable, 0 filtered.

[ekristen]

🎉 This PR is included in version 3.0.0-beta.38 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

[rstalbow]

Great! Sorry I didnt get a chance to test the build

[ekristen]

Feel free to test now and let me know if you run into issues

[ekristen]

🎉 This PR is included in version 3.0.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀