🌱 Bump CAPI to v1.8.5

[furkatgofurov7]

What this PR does / why we need it:
Follows: https://cluster-api.sigs.k8s.io/developer/providers/migrations/v1.7-to-v1.8 to bump Cluster API to v1.8.5, the latest version in v1.8.x series, as is now.

Additionally, there were a couple of changes included in the same patch, since there was a circular dependency among cluster API and controller runtime dependencies:

1. The sigs.k8s.io/controller-runtime/pkg/config/v1alpha1 package utilized in v1alpha1 of our API has been deprecated (refer to RFC: Deprecation and removal of ComponentConfig controller-runtime#895). Consequently, updating to a new Cluster API version, which removes ComponentConfig, forced us to develop a custom config loader for the v1alpha1 API. It’s important to note that we successfully transitioned from ComponentConfig to its new alternative in v1alpha2 of our API, as detailed in v1alpha2? #167 (comment), but package usage remained in v1alpha1 API.

2. The size of this patch has increased due to several interdependencies that could not be split into separate PRs (the Cluster API update requires a new controller runtime, which in turn needs a custom config). Despite this, hopefully reviewing it should be still relatively straight-forward. Key reasons for the expanded diffs include:

   • Core components in the YAML files have been swapped: from v1.5.4 & v1.6.0 to v1.7.7 & v1.8.0.
   • The upgrade of controller-gen introduced significant changes in the Custom Resource Definitions (CRDs).

3. Due to these necessary changes to v1alpha1, the api-diff CI will fail.

Which issue(s) this PR fixes (optional, in fixes #(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #566

[netlify]

✅ Deploy Preview for kubernetes-sigs-cluster-api-operator ready!

Name	Link
🔨 Latest commit	c7b9c24
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-sigs-cluster-api-operator/deploys/6732f756ea85e70008a4263b
😎 Deploy Preview	https://deploy-preview-632--kubernetes-sigs-cluster-api-operator.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[k8s-ci-robot]

@furkatgofurov7: 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-operator-apidiff-main	c7b9c24	link	false	/test pull-cluster-api-operator-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.

[salasberryfin]

Thanks @furkatgofurov7.

/lgtm

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 227ed7ea918fd5106eed36170b2fb6330d76a976

[alexander-demicev]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: alexander-demicev

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 [alexander-demicev]

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