log set of issues when node group in degraded state

[stefanSpectro]

What type of PR is this?
/kind bug

What this PR does / why we need it:
This PR implements code so that when an EKS NodeGroup goes into a Degraded state, we return the Health Issues for the given Node Group as an error. Previously an error was being returned with no context as to what happened on the AWS side. This is the first initial PR relating to the work of getting CAPA to properly reconcile Degraded Node Groups.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
https://spectrocloud.atlassian.net/browse/PCP-2384
Special notes for your reviewer:

Checklist:

• squashed commits
• includes documentation
• adds unit tests
• adds or updates e2e tests

[spectro-prow]

@stefanSpectro: The label(s) kind/bug cannot be applied, because the repository doesn't have them

In response to this:

What type of PR is this?
/kind bug

What this PR does / why we need it:
This PR implements code so that when an EKS NodeGroup goes into a Degraded state, we return the Health Issues for the given Node Group as an error. Previously an error was being returned with no context as to what happened on the AWS side. This is the first initial PR relating to the work of getting CAPA to properly reconcile Degraded Node Groups.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
https://spectrocloud.atlassian.net/browse/PCP-2384
Special notes for your reviewer:

Checklist:

• squashed commits
• includes documentation
• adds unit tests
• adds or updates e2e tests

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.

[pavansokkenagaraj]

LGTM!

[sadysnaat]

@stefanSpectro this is really great, could you please help reference upstream PR for the same.

[stefanSpectro]

@sadysnaat I have opened an upstream PR for the same code change: kubernetes-sigs#4811

Do you mind reviewing this PR in our fork? Or am I ok to merge?

[stefanSpectro]

@sadysnaat Upstream PR has been reopened and is ready for them to review. Can we review this PR for our fork in the meantime?

Upstream responses can be very delayed. This PR isnt functionally changing much it is just returning a more descriptive error. Hoping to get this into our fork without having to wait for upstream.

Let me know.

Thanks

[spectro-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: pavansokkenagaraj, snehala27, stefanSpectro
To complete the pull request process, please assign after the PR has been reviewed.
You can assign the PR to them by writing /assign in a comment when ready.

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

Needs approval from an approver in each of these files:

• OWNERS

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