Kontainer driver cluser detail does not group nodes by node pool; they are listed as not in a pool #13997
Description
Describe the bug
To Reproduce
Create an AKS, EKS, or GKE cluster through the UI
When the cluster has finished provisioning, navigate to its detail page
Result
All nodes are listed as 'not in a pool.' There is no way to scale any node pool.
Expected Result
Nodes should be grouped by pool, similar to RKE2. Any scale up/down actions should be performed by updating the cluster spec to change the pool/group configuration; not by performing actions on the node objects (as is done in rke1).
Note that this does NOT mean "use the rke2 component for kontainer driver clusters" -- the api calls to scale pools would be different and the manner in which we determine what group each management.cattle.io.node belongs to will be different. Kontainer driver clusters do not have separate 'machine pool' kubernetes resources we can reference; the grouping is defined in the cluster object itself.
Screenshots
Current kontainer cluster detail:
RKE2 grouping by pool:
Additional context