WARNING: version difference between client (1.x) and server (1.y) is displayed when running `az aks check-acr`

### **This is autogenerated. Please review and update as needed.**

## Describe the bug

az cli seems to internally use kubectl to perform the check for `az aks check-acr` this results in a warning in the output as seen in the errors section

From offcial K8s documentation

> a client should be skewed no more than one minor version from the master, but may lead the master by up to one minor version. For example, a v1.3 master should work with v1.1, v1.2, and v1.3 nodes, and should work with v1.2, v1.3, and v1.4 clients

**Command Name**
`az aks check-acr`

**Errors:**
```
az aks check-acr --resource-group foo-rg --name bar-cp --acr baz.azurecr.io Merged "bar-cp" as current context in /tmp/tmppdma83jo
WARNING: version difference between client (1.21) and server (1.19) exceeds the supported minor version skew of +/-1
Error attaching, falling back to logs: unable to upgrade connection: container canipull-013200e5-92d4-485e-8d04-a089dab73f22 not found in pod canipull-013200e5-92d4-485e-8d04-a089dab73f22_default
```

## To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

- create a managed cluster with version 1.19
- `az aks check-acr --resource-group {} --name {} --acr {}`

## Expected Behavior
No warnings
## Environment Summary
```
Linux-5.10.16.3-microsoft-standard-WSL2-x86_64-with-glibc2.2.5
Python 3.8.11
Installer: HOMEBREW

azure-cli 2.27.0 *

```
## Additional Context