Introduce Client & Region in each Resource Type + Config Resource type & name changes for consistency

[james03160927]

Description

Backward Incompatible Changes, including config name & resource type & resource names changes for consistency.

• inconsistency in naming (e..g, sometime use plural, sometime use singular)

Part of #494.

TODO: make necessary changes in nuke_sandbox and nuke_phxdevops jobs.

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].

Updated [Introduce Client & Region in each Resource Type + Config Resource type & name changes for consistency]

Migration Guide

Looking at the README page, users would have to change the resource type & name mapping in their configuration file, If they were using the configuration file to run cloud-nuke.