✨ Make KCP's patches option mutable

[superbrothers]

What this PR does / why we need it:

This PR makes KubeadmControlPlane's patches option mutable.

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

[k8s-ci-robot]

Hi @superbrothers. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[sbueringer]

Thx!

/lgtm
/ok-to-test
/assign @fabriziopandini

[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

[sbueringer]

Let's cherry-pick this PR into 1.1.

I think it's reasonable considering:

• we are doing on last 1.1 release next week
• this is a bugfix
• users might not be able to upgrade to 1.2 yet as their infra provider might not be compatible with v1.2 yet

xref: https://kubernetes.slack.com/archives/C8TSNPY4T/p1662546254345069

[sbueringer]

/cherry-pick release-1.1

[k8s-infra-cherrypick-robot]

@sbueringer: new pull request created: #7180

In response to this:

Let's cherry-pick this PR into 1.1.

I think it's reasonable considering:

• we are doing on last 1.1 release next week
• this is a bugfix
• users might not be able to upgrade to 1.2 yet as their infra provider might not be compatible with v1.2 yet

/cherry-pick release-1.1

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]

@sbueringer: new pull request could not be created: failed to create pull request against kubernetes-sigs/cluster-api#release-1.1 from head k8s-infra-cherrypick-robot:cherry-pick-6586-to-release-1.1: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"A pull request already exists for k8s-infra-cherrypick-robot:cherry-pick-6586-to-release-1.1."}],"documentation_url":"https://docs.github.com/rest/reference/pulls#create-a-pull-request"}

In response to this:

/cherry-pick release-1.1

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.