build(deps): bump google.golang.org/grpc from 1.57.1 to 1.68.0

[dependabot]

Bumps google.golang.org/grpc from 1.57.1 to 1.68.0.

Release notes

Sourced from google.golang.org/grpc's releases.

Release 1.68.0

Known Issues

• The recently added grpc.NewClient function is incompatible with forward proxies, because it resolves the target hostname on the client instead of passing the hostname to the proxy. This bug has been present since the introduction of NewClient. A fix is expected to be a part of grpc-go v1.69. (#7556)

---

Behavior Changes

• stats/opentelemetry/csm: Get mesh_id local label from "CSM_MESH_ID" environment variable, rather than parsing from bootstrap file (#7740)
• orca (experimental): if using an ORCA listener, it must now be registered only on a READY SubConn, and the listener will automatically be stopped when the connection is lost. (#7663)
• client: ClientConn.Close() now closes transports simultaneously and waits for transports to be closed before returning. (#7666)
• credentials: TLS credentials created via NewTLS that use tls.Config.GetConfigForClient will now have CipherSuites, supported TLS versions and ALPN configured automatically. These were previously only set for configs not using the GetConfigForClient option. (#7709)

Bug Fixes

• transport: prevent deadlock in client transport shutdown when writing the GOAWAY frame hangs. (#7662)
• mem: reuse buffers more accurately by using slice capacity instead of length (#7702)
  • Special Thanks: @​PapaCharlie
• status: Fix regression caused by #6919 in status.Details() causing it to return a wrapped type when getting proto messages generated with protoc-gen-go < v1. (#7724)

Dependencies

• Bump minimum supported Go version to go1.22.7. (#7624)

Release 1.67.1

Bug Fixes

• transport: Fix a bug causing stream failures due to miscalculation of the flow control window in both clients and servers. (#7667)
• xds/server: Fix xDS Server memory leak. (#7681)

Release 1.67.0

Bug Fixes

• ringhash: when used with multiple EDS priorities, fix bug that could prevent a higher priority from recovering from transient failure. (#7364)
  • Special Thanks: @​atollena

Behavior Changes

• In accordance with RFC 7540, clients and servers will now reject TLS connections that don't support ALPN. This can be disabled by setting the environment variable GRPC_ENFORCE_ALPN_ENABLED to false (case insensitive). Please file a bug if you encounter any issues with this behavior. The environment variable to revert this behavior will be removed in an upcoming release. (#7535)

Release 1.66.3

Bug Fixes

• transport: Fix a bug causing stream failures due to miscalculation of the flow control window in both clients and servers. (#7667)
• xds/server: Fix xDS Server memory leak. (#7681)

Release 1.66.2

... (truncated)

Commits

• acba4d3 Change version to 1.68.0 (#7743)
• 5363dca credentials: Apply defaults to TLS configs provided through GetConfigForClien...
• 056dc64 status: Fix status incompatibility introduced by #6919 and move non-regenerat...
• b79fb61 mem: use slice capacity instead of length, to determine whether to pool buffe...
• 54841ef stats/opentelemetry/csm: Get mesh_id local label from "CSM_MESH_ID" environme...
• ad81c20 pickfirstleaf: minor simplification to reconcileSubConnsLocked method (#7731)
• b850ea5 transport : wait for goroutines to exit before transport closes (#7666)
• 00b9e14 pickfirst: New pick first policy for dualstack (#7498)
• 18a4eac testutils: add couple of log statements to the restartable listener type (#7716)
• fdc2ec2 xdsclient: deflake TestADS_ResourcesAreRequestedAfterStreamRestart (#7720)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually 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)

[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 mowangdk 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]

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.