Adding logic to apply new hardware on tink upgrades

[pokearu]

Issue #8190:

Description of changes:
In previous EKSA upgrade workflows we had operations that were performed on a bootstrap (KinD cluster) after it came up and after CAPI was installed on it.
https://github.com/aws/eks-anywhere/blob/main/pkg/providers/tinkerbell/upgrade.go#L186
https://github.com/aws/eks-anywhere/blob/main/pkg/providers/tinkerbell/upgrade.go#L208

Now looks like these are getting skipped since we have removed the KinD cluster requirement for upgrading. That lead to the above issue. These changes add back the steps for management and workload cluster upgrades.

Testing:

./eksctl-anywhere upgrade cluster -f ./cluster.yaml -z ./new-node0102.csv

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

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 73.44%. Comparing base (2d13634) to head (aae92c9).
Report is 2 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #8288   +/-   ##
=======================================
  Coverage   73.44%   73.44%           
=======================================
  Files         578      578           
  Lines       36165    36165           
=======================================
  Hits        26561    26561           
  Misses       7917     7917           
  Partials     1687     1687           

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

[panktishah26]

/approve
/lgtm

[eks-distro-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: panktishah26

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

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

[tatlat]

/lgtm

[panktishah26]

/cherry-pick release-0.19

[eks-distro-pr-bot]

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

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.

[abhinavmpandey08]

/lgtm

[eks-distro-pr-bot]

@panktishah26: new pull request created: #8295

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.