Provide basic hierarchical data for the targeted cloud provider

This would help users stay within the CLI utility vs. grabbing said metadata to pivot on from other sources. The basic examples outlined below:

- Can be used for general info/scoping/pivoting.

- Some are required for operations (e.g. Project ID for GCP), which you may not always know/remember if you don't want to target what's configured locally

- A user may need to know every tenant/project/organization that exists so they can ensure they're grabbing data from everywhere applicable/available

## Azure
- subscriptions : `az account --list`
- tenants (not sure if this is possible)

## AWS
- list of organizations : `aws organizations list-accounts`

## GCP

- Org ID (if exists) : `gcloud organizations list --format='value(name)'`
- list of projects : `gcp projects list`
- build a visual hierarchy
It would be helpful to have some visual way to see how said GCP is set up. This would include:
- Enumerating all organizations (if any)
- Enumerating all folders (recursively, if any)
- Enumerating all projects (recursively)

Ideally, this would be some sort of “tree”, where you can easily identify:
- The type of node (organization, folder, project)
- Basic info. of said node (name, id)

Commencez par examiner les commandes CLI existantes pour AWS, Azure et GCP, puis comparez-les aux commandes des fournisseurs listées dans l’issue. Définissez la sortie et le périmètre de chaque fournisseur avant d’implémenter la découverte. Le travail devra inclure les informations disponibles sur l’organisation, le tenant, l’abonnement, le dossier et le projet, avec une hiérarchie GCP lisible affichant le type, le nom et l’ID de chaque nœud.

Rédigé par le modèle d'indexation à partir du texte de l'issue.