Create infrastructure for kubebuilder artifacts

[rikatz]

Per #2647

kubebuilder folks need to regain access to old GCP projects, and while discussing with @camilamacedo86 how to achieve this, I've figured out this could be an opportunity for now on to migrate new artifacts to community owned infrastructure.

This PR is split on 4 commits and:

• Creates the new google group for kubebuilder staging under sig-apimachinery
• Creates the required project for kubebuilder staging
• Creates the required image promotion manifests after cloudbuild prow job for kube-rbac-proxy runs
• Creates the required filestore promotion manifest after cloudbuild prowjob for kubebuilder-tools runs DROPPED THIS COMMIT AS IT NEEDS PREVIOUS STUFF TO BE DONE

After this PR gets merged, there are still some follow up actions:

• Add two prowjobs post submit for the specific kubebuilder repo branches, to run cloudbuild for kube-rbac-proxy and tools and respectively send the artifacts to the right staging places
• Check/fix cloudbuild yaml files on kubebuilder to use Kubernetes cloudbuild required patterns
• Update kubebuilder release process, to reflect the fact that after cloud build jobs runs, one should go to k8s.io repo, on the image promotion manifests, and request the promotion of the artifacts to the prod buckets/filestore/gcr

[k8s-ci-robot]

@rikatz: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-k8sio-file-promo	219cde7	link	true	/test pull-k8sio-file-promo

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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.

[dims]

/approve
/lgtm

@rikatz landing this now, please ping me back if any of the resources are not created in say an hour or so after this merges.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dims, rikatz

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 [dims]
• groups/OWNERS [dims]

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

[rikatz]

Just saw this @dims thanks! I will add myself to the groups to check if everything is working fine, and I've reached @camilamacedo86 to help on this migration. If she and kubebuilder team are ok with this,I will help on migration then remove myself.

Thanks!

[camilamacedo86]

I think we need add here @vincepri and @sbueringer (if they agree with)

This one will probably only used for we build and promote : kubernetes-sigs/kubebuilder-release-tools#60 so far