Confirm by changing [ ] to [x] below to ensure that it's a bug:

• I've gone though the User Guide and the API reference
• I've searched for previous similar issues and didn't find any solution

Describe the bug
Versions 1.20.9 and 2.2.24 shipped a breaking change to EKS support by changing the supported k8s API value from v1alpha1 to v1beta1. This breaks any existing kubeconfigs that have v1alpha1 specified in their kubeconfig.

The PR that changed this behavior clearly specified this is a breaking change, however the changed shipped in a point release, with no clear communication about it being a breaking change.

The error message you see when attempting to use a kubeconfig with an incorrect version is:

unable to use kubectl with the EKS cluster (check 'kubectl version'): Unable to connect to the server: getting credentials: exec plugin is configured to use API version client.authentication.k8s.io/v1alpha1, plugin returned version client.authentication.k8s.io/v1beta1

SDK version number
1.20.9
2.2.24

Platform/OS/Hardware/Device
What are you running the cli on?

Linux/Mac OS X

To Reproduce (observed behavior)

1. Have a kubeconfig that uses eks get-token for authentication
2. Upgrade CLI to 1.20.9 or 2.2.24
3. Run a kubectl command

Expected behavior
Point releases of CLIs to not include breaking changes

Logs/output

unable to use kubectl with the EKS cluster (check 'kubectl version'): Unable to connect to the server: getting credentials: exec plugin is configured to use API version client.authentication.k8s.io/v1alpha1, plugin returned version client.authentication.k8s.io/v1beta1

Additional context
Related to aws-samples/eks-workshop#1232