Early Day Idea: U/X Re-design estimate work for thinking for adding Fleet like concept in the VsCode Extension.

### Idea

We should get some input from the U/X designer as to how we can accomodate the enablement and idea of enabling Fleet Manager via this extension:

* https://learn.microsoft.com/en-us/azure/kubernetes-fleet/overview
* https://learn.microsoft.com/en-us/azure/kubernetes-fleet/concepts-update-orchestration

> Platform admins managing large number of clusters often have problems with staging the updates of multiple clusters (for example, upgrading node OS image versions, upgrading Kubernetes versions) in a safe and predictable way. To address this pain point, Azure Kubernetes Fleet Manager (Fleet) allows you to orchestrate updates across multiple clusters using update runs, stages, groups, and strategies. [read more](https://learn.microsoft.com/en-us/azure/kubernetes-fleet/concepts-update-orchestration)

### Initial thoughts:

We have node trees on the left hand side cloud explorer for this extension, we could think of somehow adding some sort of flag next to each cluster to represent the name of fleet that cluster belong to and upon selecting that `info` ℹ️ button user can see the whole fleet and cluster under it in much details.

Review the Azure Kubernetes Fleet overview and update-orchestration documentation, then inspect the existing VS Code Cloud Explorer cluster tree described in the issue. Use linked PR #1150 as context and define the UX scope for showing fleet membership and details; done means an agreed estimate and design direction, not implementation.

Written by the indexing model from the issue text.