Custom exec auth breaks compatibility with tools like kubectl

To avoid bundling kubelogin, aks-desktop configures AKS clusters with a custom Python exec authentication script.

While this works within the app, the generated kubeconfig is non-standard and not compatible with tools like kubectl or other Kubernetes clients. This can confuse users and lead to unexpected auth failures outside the app.

The custom script also introduces a maintenance risk, it can become outdated as AKS/Azure auth flows change, and there is no clear strategy to keep existing users in sync without shipping a new app release.

We need to decide whether this approach is sustainable or if we should move to a standard AKS authentication mechanism with clearer upgrade and compatibility guarantees.

Estimate (stateless clusters) 1-2 weeks

Start by reviewing how AKS Desktop generates kubeconfig files and invokes the custom Python exec authentication script. Compare that approach with standard AKS authentication used by kubectl and other Kubernetes clients; the work is done when a sustainable mechanism and upgrade strategy are defined that preserve compatibility for existing users.

Written by the indexing model from the issue text.