Update google.golang.org/genproto

[liggitt]

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

Updates to a version of google.golang.org/genproto with generic packages carved into submodules (googleapis/go-genproto#1012)

These still include a backreference to the root google.golang.org/genproto module, but only for a period of time while consumers are transitioning to the new isolated modules.

xref #113366

See googleapis/go-genproto#1015 for details on the timeline for completing the submodule isolation.

This increases the total number of dependencies in our graph because it updates to a cloud.google.com/go that carved out submodules for every API:

-Direct Dependencies: 205 
-Transitive Dependencies: 228 
-Total Dependencies: 277 
-Max Depth Of Dependencies: 23 
+Direct Dependencies: 209 
+Transitive Dependencies: 341 
+Total Dependencies: 390 
+Max Depth Of Dependencies: 17

That's unfortunate in the short-term, but does not actually increase the number of vendored/built dependencies significantly, and unblocks several other dependency updates. Once genproto rpc/api/bytestream packages drop the back-reference to the root genproto library on 2024-03-01, we can drop those dependencies from our graph.

Does this PR introduce a user-facing change?

NONE

/area code-organization
/assign @dims

[jpbetz]

Thanks @liggitt! We need badly to allow us to continue to bump to new versions of CEL. I appreciate all the work you did to coordinate with the genproto maintainers to set up firm plan that allows us to remove unneeded transitive deps long-term.

/lgtm

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 6ae9143a6d876d1b65280b68c519f49d23e96d69

[liggitt]

/hold
thanks for the review, wanted to give @dims a chance to review as well
unhold once that is done

[liggitt]

/retest
existing flake on CRD validating schema - https://storage.googleapis.com/k8s-triage/index.html?text=failed%20to%20wait%20for%20OpenAPI%20spec%20validating%20condition

[dims]

+100 to what @jpbetz said. Glad there is a firm plan to clear this debt we are picking up now.

/approve
/lgtm
/hold cancel

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

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

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,liggitt]
• LICENSES/OWNERS [dims,liggitt]
• hack/OWNERS [dims,liggitt]
• staging/src/k8s.io/apiextensions-apiserver/OWNERS [dims,liggitt]
• staging/src/k8s.io/apiserver/OWNERS [dims,liggitt]
• staging/src/k8s.io/cli-runtime/OWNERS [dims,liggitt]
• staging/src/k8s.io/client-go/OWNERS [dims,liggitt]
• staging/src/k8s.io/cloud-provider/OWNERS [dims,liggitt]
• staging/src/k8s.io/code-generator/OWNERS [dims,liggitt]
• staging/src/k8s.io/component-base/OWNERS [dims,liggitt]
• staging/src/k8s.io/component-helpers/OWNERS [dims,liggitt]
• staging/src/k8s.io/controller-manager/OWNERS [dims,liggitt]
• staging/src/k8s.io/cri-api/OWNERS [dims,liggitt]
• staging/src/k8s.io/dynamic-resource-allocation/OWNERS [dims,liggitt]
• staging/src/k8s.io/kms/OWNERS [dims,liggitt]
• staging/src/k8s.io/kube-aggregator/OWNERS [dims,liggitt]
• staging/src/k8s.io/kubectl/OWNERS [dims,liggitt]
• staging/src/k8s.io/kubelet/OWNERS [dims,liggitt]
• staging/src/k8s.io/legacy-cloud-providers/OWNERS [dims,liggitt]
• staging/src/k8s.io/metrics/OWNERS [dims,liggitt]
• staging/src/k8s.io/pod-security-admission/OWNERS [dims,liggitt]
• staging/src/k8s.io/sample-apiserver/OWNERS [dims,liggitt]
• staging/src/k8s.io/sample-cli-plugin/OWNERS [dims,liggitt]
• staging/src/k8s.io/sample-controller/OWNERS [dims,liggitt]
• vendor/OWNERS [dims,liggitt]

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

[cici37]

/triage accepted