Add failure domains into missing permissions logic

[charles-large]

Issue #, if available:
issue
Description of changes:

• Adjusted missing permissions code to take a common interface between vspheremachineconfigs and failuredomains to compare similar values
• Added compute cluster permissions checking (using AdminPrivs file)
• Unit testing
• Here is an example missing permissions output when user has no permissions.

[codecov]

Codecov Report

Attention: Patch coverage is 97.56098% with 2 lines in your changes missing coverage. Please review.

Project coverage is 69.75%. Comparing base (f33e91e) to head (1da52b1).
Report is 17 commits behind head on main.

Files with missing lines	Patch %	Lines
pkg/providers/vsphere/validator.go	96.61%	2 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #9612      +/-   ##
==========================================
+ Coverage   69.73%   69.75%   +0.02%     
==========================================
  Files         672      672              
  Lines       49550    49616      +66     
==========================================
+ Hits        34555    34612      +57     
- Misses      13219    13226       +7     
- Partials     1776     1778       +2     

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[rajeshvenkata]

/lgtm
/approve

[eks-distro-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rajeshvenkata

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 [rajeshvenkata]

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

[rajeshvenkata]

/cherry-pick release-0.22

[eks-distro-pr-bot]

@rajeshvenkata: once the present PR merges, I will cherry-pick it on top of release-0.22 in a new PR and assign it to you.

In response to this:

/cherry-pick release-0.22

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.

[eks-distro-pr-bot]

@rajeshvenkata: new pull request created: #9647

In response to this:

/cherry-pick release-0.22

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.