Show active capella org in cbenv output when set

[Westwooo]

Currently when we run the cb-env command it only shows the capella org associated with the active cluster. This can lead to confusion since the org associated with the active cluster is not necessarily the same as the active org :

> cb-env
╭──────────────────────┬───────────────╮
│ username             │ Administrator │
│ display_name         │ Westwooo      │
│ cluster              │ remote        │
│ bucket               │ default       │
│ scope                │ _default      │
│ collection           │ _default      │
│ cluster_type         │ other         │
│ capella-organization │ my-org        │
│ llm                  │ OpenAI        │
╰──────────────────────┴───────────────╯
👤 Westwooo 🏠 remote in 🗄 default._default._default
> projects
Error:   × Unexpected status code
   ╭─[entry #2:1:1]
 1 │ projects
   · ────┬───
   ·     ╰──
   ╰────
  help: Unexpected status code: 401, body: {"code":1001,"hint":"The request is unauthorized. Please ensure you have provided appropriate credentials in the request header. Please make sure the client IP that is trying to access the
        resource using the API key is in the API key allowlist.","httpStatusCode":401,"message":"Unauthorized"}


👤 Westwooo 🏠 remote in 🗄 default._default._default
> cb-env --capella
╭──────────────────────┬────────────╮
│ capella-organisation │ not-an-org │
│ project              │            │
│ llm                  │ OpenAI     │
╰──────────────────────┴────────────╯

It initially seems that we are unauthorised to connect to the org my-org however we can see that the active capella org is actually not-an-org which is the org used in the running of the projects command. To make this less confusing thisi PR removes the capella flag from cb-env and always shows the active org and differentiates it from the cluster org:

👤 Westwooo 🏠 remote in 🗄 default._default._default
> cb-env
╭──────────────────────┬───────────────╮
│ username             │ Administrator │
│ display_name         │ Westwooo      │
│ cluster              │ remote        │
│ bucket               │ default       │
│ scope                │               │
│ collection           │               │
│ cluster_type         │ other         │
│ cluster-organization │ my-org        │
│ active-organization  │ not-an-org    │
│ project              │               │
│ llm                  │ OpenAI        │
╰──────────────────────┴───────────────╯

Another solution considered was to make the cluster-organization of the active cluster the active-organization. But this means that we would be changing the active org when changing the active cluster, which doesn't feel right considering orgs are higher level entities than clusters. Also we want to have an active org without having to have an active cluster.