Part of umbrella issue to migrate away from google.com gcp projects: #1469

We didn't notice this because it doesn't show up anywhere in kubernetes/test-infra, but apparently kubebuilder uses a google-internal project (ref: #1469 (comment))

We need help from someone from the subproject who has access to scope out what exactly is used and determine how best to migrate, e.g.

• maybe this can be satisfied by a k8s-staging-kubebuilder project?
• maybe the staging project needs some special-case functionality enabled?
• eg.

/wg k8s-infra
/sig api-machinery
/priority important-soon
/milestone v1.23

/assign @leilajal
I'm assigning to you to help with scoping out how the internal project is used and what needs to be moved over. Feel free to reassign to someone who is more familiar with kubebuilder's release process