chore: bump google.golang.org/grpc/cmd/protoc-gen-go-grpc from 1.3.0 to 1.5.1 in /hack/tools

[dependabot]

Bumps google.golang.org/grpc/cmd/protoc-gen-go-grpc from 1.3.0 to 1.5.1.

Release notes

Sourced from google.golang.org/grpc/cmd/protoc-gen-go-grpc's releases.

protoc-gen-go-grpc v1.5.1

Dependencies

• Removed replace directive (needed only for testing), since it is incompatible with go install (#7451).

protoc-gen-go-grpc v1.5.0

Security

• The generated function Register<Service>Server now panics if the Unimplemented<Service>Server struct is embedded in a way that would otherwise lead to runtime panics if an unimplemented method was called. Users are advised to ensure they are properly embedding the Unimplemented struct for their service, and to regenerate their proto files to confirm. (#7438)
  • Note: "Proper embedding" of the Unimplemented struct means either embedding the struct by value (preferred) or ensuring it is always initialized to a valid pointer. E.g.

struct MyServiceImpl {
	pb.UnimplementedMyServiceServer // embedded by value, not pointer
	// .. other struct fields ..
}

New Features

• Generated code for services will produce streaming method definitions using one of six different generic types (e.g. BidiStreamingServer or ClientStreamingClient) instead of producing complete interfaces and implementations for the streaming methods. This can be disabled by setting use_generic_streams_experimental=false. Please file a bug if you encounter any issues with this behavior. (#7387)

Bug Fixes

• A period (.) is added to the end of the service interface doc comment to comply with Godoc. (#7392)

protoc-gen-go-grpc v1.4.0

New Features

• Add an optional implementation of streams using generics (Experimental) (#7057)
  • The new use_generic_stream_experimental=true option will cause the gRPC codegen to use prebuilt generic types to implement client and server stream objects, rather than generating new types and implementations for every RPC method. We intend to transition this to the default behavior in the next release. Please test it and provide any feedback.
  • Special Thanks: @​aarongable
• Copy service comments to interfaces in generated code (#7243)
  • Special Thanks: @​silves-xiang
• Generated code includes static method gRPC call options for integration with the upcoming OpenTelemetry metrics support (#6960)

Dependencies

• Update google.golang.org/protobuf dependency to v1.34.1 to address CVE-2024-24786 (#7274)

Commits

• b8669c3 Change version to 1.5.1
• 5ad7775 Do not create new addrConn when connection error happens (#1369)
• 284c78b Change version to 1.5.1-dev
• 172ccac Change version to 1.5.0
• 939edc0 Revert "Use bufconn in end2end tests." (#1381)
• 71260d2 Fix logging method (#1375)
• c7e2c00 Use bufconn in end2end tests.
• 9a71c79 Create bufconn package for a local, buffered net.Conn and dialer/listener
• ce03e9c Fix a typo in examples/gotutorial.md (#1374)
• d672391 Use log severity and verbosity level (#1340)
• Additional commits viewable in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[k8s-ci-robot]

Hi @dependabot[bot]. 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-sigs/prow repository.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: dependabot[bot]
Once this PR has been reviewed and has the lgtm label, please assign ritazh for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

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

[k8s-ci-robot]

PR needs rebase.

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-sigs/prow repository.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle stale
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale