[Feature Request] Setup organization heirarchy

[golanglemonade]

Example structure:

├── datum_controlled_top_level <-- this would be an org we could configure with things like our posthog infos
│   └── rootorg <--- top level customer org
│       ├── production <-- top level environment per customer org
│       │   ├── assets
│       │   ├── customers
│       │   ├── orders
│       │   ├── relationships
│       │   │   ├── internal_users
│       │   │   ├── marketing_subscribers
│       │   │   ├── marketplaces
│       │   │   ├── partners
│       │   │   └── vendors
│       │   └── sales
│       └── test <-- org identical to production just named differently to give customer 2 sandboxes to configure
└── systemorg <-- database seeded org to avoid circular deps / inception bullshit

All the child organizations will either be created via a hook, or possibly a single graph mutation such as:

{
  "input": {
    "name": "meow",
    "createChildOrganizations": [
      {
        "name": "production",
        "createChildOrganizations" : [
          {"name": "assests"},
          {"name": "customers"},
          {"name": "orders"},
          {"name": "sales"},
          {"name": "relationships",
          "createChildOrganizations": [
            {"name": "internal_users"},
            {"name": "marketing_subscribers"},
            {"name": "marketplaces"},
            {"partners": "vendors"},
          ]
          },
          
        ],
      },
    ],
  },
}

[golanglemonade]

Resolved with this PR in datum-cloud: https://github.com/datumforge/datum-cloud/pull/12