bump kubebuilder-tools to 1.20.2

[zmalik]

What type of PR is this?
/kind cleanup

What this PR does / why we need it:
we are seeing tests fails in local dev environments with macOS 12:

Panic [0.458 seconds]
[BeforeSuite] BeforeSuite
/Users/cerobert/go/src/sigs.k8s.io/cluster-api-provider-azure/controllers/suite_test.go:48

  Test Panicked
  unable to start control plane itself: failed to start the controlplane. retried 5 times: timeout waiting for process etcd to start successfully (it may have failed to start, or stopped unexpectedly before becoming ready)
  /Users/cerobert/go/src/sigs.k8s.io/cluster-api-provider-azure/internal/test/env/env.go:107

which is caused by etcd failing to start up

❯ hack/tools/bin/etcd                                                                                                                                                                                                                      
fatal error: runtime: bsdthread_register error

runtime stack:
runtime.throw(0x1bed3fa, 0x21)
	/usr/local/go/src/runtime/panic.go:616 +0x81 fp=0x7ff7bfeff378 sp=0x7ff7bfeff358 pc=0x102a871
runtime.goenvs()
	/usr/local/go/src/runtime/os_darwin.go:129 +0x83 fp=0x7ff7bfeff3a8 sp=0x7ff7bfeff378 pc=0x10283f3
runtime.schedinit()
	/usr/local/go/src/runtime/proc.go:501 +0xd6 fp=0x7ff7bfeff410 sp=0x7ff7bfeff3a8 pc=0x102d166
runtime.rt0_go(0x7ff7bfeff440, 0x1, 0x7ff7bfeff440, 0x1000000, 0x1, 0x7ff7bfeff650, 0x0, 0x7ff7bfeff664, 0x7ff7bfeff6a0, 0x7ff7bfeff6e2, ...)
	/usr/local/go/src/runtime/asm_amd64.s:252 +0x1f4 fp=0x7ff7bfeff418 sp=0x7ff7bfeff410 pc=0x1056474

which can be root caused to https://github.com/golang/go/wiki/MacOS12BSDThreadRegisterIssue

This PR proposes to bump the etcd version that is installed via kubebuilder-tools, we cannot go to the latest as we hit another unresolved issue kubernetes-sigs/controller-runtime#1571

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 #

Special notes for your reviewer:

Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.

TODOs:

• squashed commits
• includes documentation
• adds unit tests

Release note:

NONE

[k8s-ci-robot]

Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA.

It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.

---

• If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
• If you signed the CLA as a corporation, please sign in with your organization's credentials at https://identity.linuxfoundation.org/projects/cncf to be authorized.
• If you have done the above and are still having issues with the CLA being reported as unsigned, please log a ticket with the Linux Foundation Helpdesk: https://support.linuxfoundation.org/
• Should you encounter any issues with the Linux Foundation Helpdesk, send a message to the backup e-mail support address at: [email protected]

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

[linux-foundation-easycla]

• ❌ The commit (eb9dad0) is missing the User's ID, preventing the EasyCLA check. Consult GitHub Help to resolve.For further assistance with EasyCLA, please submit a support request ticket.

[k8s-ci-robot]

Hi @zmalik. 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.

[sonasingh46]

Thank you. I have verified it. This fixes the issue.
Also, does this mean that the etcd binary that was causing the issue was built on go 1.10 or before?

[zmalik]

does this mean that the etcd binary that was causing the issue was built on go 1.10 or before?

looks like [email protected] was using etcd 3.3.11 which was build on go 1.10.3

[CecileRobertMichon]

/ok-to-test

[CecileRobertMichon]

Code="ResourceGroupBeingDeleted" Message="The resource group 'capz-4wno1n' is in deprovisioning state and cannot perform this operation."" "name"="capz-4wno1n" "namespace"="default" "reconciler group"="infrastructure.cluster.x-k8s.io" "reconciler kind"="AzureCluster"

looks like there might have been a collision in random RG naming?

/retest

[CecileRobertMichon]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: CecileRobertMichon

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

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