CORE-188 rate limits

[ellisonc]

Description

Reduces the batch sizes on all resources where the AWS rate limits were a guess such that two instances of cloud nuke could be running on an account without expecting any issues. This should enable cloud-nuke to run better in automated environments as well as reduce the likelihood of manual activity in the AWS account interfering.

This is a stopgap solution to the rate limit issue and we plan to implement a more robust approach in the future.

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)

Updated max batch size on many resources to reduce rate limit errors.

[pete0emerson]

LGTM. Stop-gap measure. Let's roll with it.