✨ Implement core logic for chained upgrades

[fabriziopandini]

What this PR does / why we need it:
This PR implements the core upgrade logic for chained upgrades.
It include also the KubernetesVersions field in CC and refactoring the E2E tests for runtime SDK to test chained upgrades

Which issue(s) this PR fixes:
Part of #12720

/area clusterclass

[sbueringer]

Opened a PR against your PR to fix some of the minor findings: fabriziopandini#312
(I also resolved the corresponding conversations)

[sbueringer]

/test pull-cluster-api-e2e-main

[k8s-ci-robot]

@fabriziopandini: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-cluster-api-apidiff-main	1c4c680	link	false	/test pull-cluster-api-apidiff-main

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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-sigs/prow repository. I understand the commands that are listed here.

[sbueringer]

/lgtm
/approve

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 454906f6c111dee2a2b572b4e48a1751c5d634e0

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sbueringer

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

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