Support multiple AWS Orgs

[WillNye]

Is your feature request related to a problem? Please describe.
Currently, I need a dedicated repo for each of my AWS Orgs. This is more difficult to maintain and reduces visibility.

Describe the solution you'd like
The ability to configure multiple orgs for a single iambic repo. It should be done in such a way that cross org insights can be used in the future.

Community Engagement
Help us prioritize this request and express your support by adding a 👍 reaction to the original issue. This will assist both the community and the maintainers in addressing this request.

Please avoid leaving "+1" or "me too" comments as they create extra noise for issue followers and do not assist in prioritizing the request. If you are considering working on this issue or have already submitted a pull request, kindly leave a comment.

[WillNye]

Some of the basic requirements I've put together so far but still a WiP.

• Update the way the aws config plugin parser works
  • Look for a path by org name
    • Fall back to the original path if not found
• Update CLI commands to optionally support an Org name flag
  • Run all orgs if one is not specified
• Update CLI commands to optionally support an exclude provider flag
• Add CLI command to list orgs
• Ability to add multiple Orgs in the CLI
  • Check for Repo structure
    • If not org segmented
      • Prompt for name for the Org that has already been setup
        • And no name set
      • Restructure the AWS Repo
        • aws
          • org_name | org_id
            • ...
      • Advise user to update their git workflows if they exist
        • Exclude the AWS provider on existing workflows
          • Give them the command to do so
        • Add the necessary workflows for the existing org
• Update the AWS github workflow docs to include a multi-org flow

There is a lot of provider specific options being mentioned as it relates to the CLI. The implementation will need to be provider agnostic for the CLI commands so thought must be given to that.

Also, I haven't made it a req because I haven't come up with the best way to handle it but flows where standalone accounts are added in the multi-org flow must be supported. Example:

• Account A from Org 2 is configured in IAMbic
• Org 1 is added to IAMbic
• Account A moves to own space within the AWS path of the users IAMbic repo
• Org 2 is added to IAMbic
• Account A path is removed now that has been added to
• At no point should the resources for Account A be removed in the flow. This could happen in theory as the file is detected as deleted in the github flow. So, a check should be made to ensure it wasn't simply moved somewhere else.

Documen