Add preflight validation to check management components vs cluster components version skew

[cxbrowne1207]

Issue #, if available:

Description of changes:
We have added to the docs that the suppported version difference of management components can be at most 1 EKS Anywhere minor version greater than the EKS Anywhere version of cluster components. However, we have no pre-flight validation that ensures that. This PR adds that preflight validation.

Testing (if applicable):

• Unit testing
• Manual testing:
  • Created cluster with v0.19.0 release
  • Upgraded management components with main

s-1-27-eks-22"}
2024-03-06T22:22:54.328Z        V0      ✅ Vsphere provider setup and validation
2024-03-06T22:22:54.328Z        V6      Getting KubeadmControlPlane CRDs        {"cluster": "mgmt"}
2024-03-06T22:22:54.328Z        V6      Executing command       {"cmd": "/usr/bin/docker exec -i eksa_1709763772371803610 kubectl get kubeadmcontrolplanes.controlplane.cluster.x-k8s.io mgmt -o json --kubeconfig mgmt/mgmt-eks-a-cluster.kubeconfig --namespace eksa-system"}
2024-03-06T22:22:54.525Z        V0      ✅ Control plane ready
2024-03-06T22:22:54.525Z        V6      Executing command       {"cmd": "/usr/bin/docker exec -i eksa_1709763772371803610 kubectl get customresourcedefinition clusters.cluster.x-k8s.io --kubeconfig mgmt/mgmt-eks-a-cluster.kubeconfig"}
2024-03-06T22:22:54.692Z        V0      ✅ Cluster CRDs ready
2024-03-06T22:22:54.692Z        V6      Executing command       {"cmd": "/usr/bin/docker exec -i eksa_1709763772371803610 kubectl get clusters.anywhere.eks.amazonaws.com -A -o jsonpath={.items[0]} --kubeconfig mgmt/mgmt-eks-a-cluster.kubeconfig --field-selector=metadata.name=mgmt"}
2024-03-06T22:22:54.911Z        V0      ✅ Validate management components version to cluster version skew
2024-03-06T22:22:54.911Z        V4      Task finished   {"task_name": "validate", "duration": "2.067429957s"}
2024-03-06T22:22:54.911Z        V4      ----------------------------------
2024-03-06T22:22:54.911Z        V4      Task start      {"task_name": "upgrade-core-components-mc"}
2024-03-06T22:22:54.911Z        V0      Upgrading core components
2024-03-06T22:22:54.911Z        V6      Executing command       {"cmd": "/usr/bin/docker exec -i eksa_1709763772371803610 kubectl get --ignore-not-found -o json --kubeconfig mgmt/mgmt-eks-a-cluster.kubeconfig EKSARelease.v1alpha1.anywhere.eks.amazonaws.com --namespace eksa-system eksa-v0-19-0"}
2024-03-06T22:22:55.082Z        V6      Executing command       {"cmd": "/usr/bin/docker exec -i eksa_170

Documentation added/planned (if applicable):

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[eks-distro-bot]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[codecov]

Codecov Report

Attention: Patch coverage is 39.28571% with 17 lines in your changes are missing coverage. Please review.

Project coverage is 73.54%. Comparing base (7ba9b3c) to head (b79ffea).
Report is 8 commits behind head on main.

❗ Current head b79ffea differs from pull request most recent head 150d868. Consider uploading reports for the commit 150d868 to get more accurate results

Files	Patch %	Lines
...kflows/management/upgrade_management_components.go	0.00%	10 Missing ⚠️
pkg/validations/cluster.go	64.70%	3 Missing and 3 partials ⚠️
...eksctl-anywhere/cmd/upgrademanagementcomponents.go	0.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #7800      +/-   ##
==========================================
- Coverage   73.55%   73.54%   -0.02%     
==========================================
  Files         588      588              
  Lines       37176    37200      +24     
==========================================
+ Hits        27346    27357      +11     
- Misses       8035     8045      +10     
- Partials     1795     1798       +3     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[cxbrowne1207]

/approve

[eks-distro-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cxbrowne1207

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [cxbrowne1207]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[cxbrowne1207]

/cherry-pick release-0.19

[eks-distro-pr-bot]

@cxbrowne1207: new pull request created: #7812

In response to this:

/cherry-pick release-0.19

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.