AWS native EKS Auth using 'Kubernetes Service Connection'

Could we have a 'Kubernetes Service Connection' that supports rotating EKS tokens as they expire.

Given there is a considerable number of plugins that support 'Kubernetes Service Connection' it would be better if you could make a provider for the 'Kubernetes Service Connection' that can use a role from an AWS 'Service Connection' provider to regenerate the token after it expires.

The process for doing this is running aws eks get-token --name $CLUSTER_NAME when assumed as a role that has been directly bound to a system role within Kubernetes.

I currently use the AWS CLI shell plugin to generate this token and pass it to the native helm release / other plugins via environment... We use the AWS Service Connection extensively and VSTS can now use a 'Kubernetes Service Connection' directly for many plugins and features.

It's also worth mentioning all our VSTS agents run EKS and use IAM roles via Kube2IAM

Start by locating the existing AWS Service Connection and Kubernetes Service Connection providers, then review how they pass credentials to Azure DevOps plugins. Compare the required flow with `aws eks get-token --name $CLUSTER_NAME` and role assumption. Done means a Kubernetes connection can use an AWS connection to refresh EKS tokens as they expire.

Written by the indexing model from the issue text.