[STSK21] Detailed module use instructions

[vexance]

Moving forward, all modules must contain detailed step-by-step instructions on module setup/use prior to merge into the dev branch. This issue is opened to task documentation of current module instructions:

• aws/enum/authed/enum_privileges_bruteforce
• aws/enum/authed/get_principal_name_noisy
• aws/enum/authed/get_principal_name_stealth
• aws/enum/unauth/enum_iam_principles
• aws/enum/unauth/enum_public_ebs_snapshots
• aws/enum/unauth/enum_s3_buckets
• aws/enum/unauth/get_account_for_access_key
• aws/enum/unauth/get_account_via_public_s3
• aws/util/assume_role_sts
• aws/util/export_public_ebs_snapshot
• aws/util/generate_console_sso_link
• aws/util/iam_console_login
• aws/util/s3_explorer_client
• gcp/enum/unauth/enum_storage_buckets

For example, Module._info['Details'] will contain a brief description of what is happening behind the scenes, and then any step-by-step instructions for use. Links used within the instructions should point to instructional documentation markdown within this repository (Links contained with the References can / should go to external sources).

[vexance]

Note: for modules with extensive / very long details for required setup and/or use, prepare a markdown doc within the Stratustryke/docs/ under a similar directory path to the module's search name. If a markdown doc is specified, the details field in the module's info can then simply reference the markdown doc.