🐛 Fix APIVersion in OwnerReferences to ClusterResourceSets

[chrischdi]

What this PR does / why we need it:

Issue got introduced in #6989 .

The introduced change creates an OwnerReference at the ClusterResourceSetBinding which looks like as follows:

    - apiVersion: addons.cluster.x-k8s.io/v1beta1, Kind=ClusterResourceSet
      kind: ClusterResourceSet
      name: self-hosted-64pplg-crs-0
      uid: 630b7f3c-babd-409e-837a-d6a849729b9d

This fix adjusts it to be:

    - apiVersion: addons.cluster.x-k8s.io/v1beta1
      kind: ClusterResourceSet
      name: self-hosted-64pplg-crs-0
      uid: 630b7f3c-babd-409e-837a-d6a849729b9d

Without the fix, clusterctl move is broken because it tries to get an ClusterResourceSet of APIVersion addons.cluster.x-k8s.io/v1beta1, Kind=ClusterResourceSet which does not exist on the client and thus results in the following error:

error reading "addons.cluster.x-k8s.io/v1beta1, Kind=ClusterResourceSet, Kind=ClusterResourceSet" /: no matches for kind "ClusterResourceSet" in version "addons.cluster.x-k8s.io/v1beta1, Kind=ClusterResourceSet"

This should cleanup the testgrid: https://testgrid.k8s.io/sig-cluster-lifecycle-cluster-api#capi-e2e-main

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 #

[k8s-ci-robot]

@chrischdi: This issue is currently awaiting triage.

If CAPI contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

[killianmuldoon]

/cherry-pick release-1.2

[k8s-infra-cherrypick-robot]

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

In response to this:

/cherry-pick release-1.2

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.

[killianmuldoon]

/lgtm

[fabriziopandini]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: fabriziopandini

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

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

[fabriziopandini]

/cherry-pick release-1.2

[k8s-infra-cherrypick-robot]

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

In response to this:

/cherry-pick release-1.2

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.

[k8s-infra-cherrypick-robot]

@killianmuldoon: new pull request created: #7024

In response to this:

/cherry-pick release-1.2

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.