🌱 Use envtest binaries from controller-tools repo

[mboersma]

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

Updates setup-envtest to a commit on main that fetches envtest binaries from the GitHub release on the controller-tools repo. This is to move away from using GCP resource buckets.

Which issue(s) this PR fixes:
Fixes #250
See also:

• 🌱 Use setup-envtest from CR main (05/2024) to use envtest binaries from CT releases cluster-api#10569
• ✨ setup-envtest: download binaries from controller-tools releases controller-runtime#2811
• Migrate away from google.com gcp project kubebuilder kubernetes/k8s.io#2647

[mboersma]

/retest

  [FAILED] Unexpected error:
      <*fmt.wrapError | 0xc00056a600>: 
      unable to start control plane itself: failed to start the controlplane. retried 5 times: exec: "etcd": executable file not found in $PATH

?

[Jont828]

/retest

[Jont828]

@mboersma Is there some kind of breaking change here/is this a version bump?

[mboersma]

Is there some kind of breaking change here?

Apparently so, although it was a smooth update for CAPZ. I'll take a look.

[mboersma]

I think the CI failure will be fixed by kubernetes/test-infra#32803.

[mboersma]

/retest

[mboersma]

/retest

[mboersma]

@Jont828 it's passing now after changing the test-infra job not to pin the kubebuilder envtest version.

[Jont828]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Jont828, mboersma

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 [Jont828,mboersma]

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