build(deps): bump google.golang.org/grpc from 1.70.0 to 1.71.0 in /tekton/ci/cluster-interceptors/add-pr-body in the all group

[dependabot]

Bumps the all group in /tekton/ci/cluster-interceptors/add-pr-body with 1 update: google.golang.org/grpc.

Updates google.golang.org/grpc from 1.70.0 to 1.71.0

Release notes

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

Release 1.71.0

API Changes

• balancer: Custom LB policies that record metrics must use the new MetricsRecorder method on Balancer.ClientConn instead of the removed Balancer.BuildOptions.MetricsRecorder field to obtain a metrics recorder. (#8027)
• balancer: balancer.ClientConn implementations must now embed a delegate implementation. This allows grpc-go to add new methods to the interface and remain backward compatible. (#8026)
• balancer/endpointsharding: The constructor accepts the child balancer's builder and a struct with optional configuration. (#8052)

New Features

• xds: Add support for dualstack via the additional_addresses field in the Endpoint resource. To disable this feature, set the environment variable GRPC_EXPERIMENTAL_XDS_DUALSTACK_ENDPOINTS=false. (#8134)
• stats/opentelemetry: Add experimental support for OpenTelemetry tracing. (#7852)
• xds/internal/xdsclient: Add counter metrics for valid and invalid resource updates. (#8038)
• balancer/leastrequest, roundrobin: Add dualstack support. (#7969, #7966)
• balancer/endpointsharding: Balancers created with the new DisableAutoReconnect option will not attempt to call ExitIdle automatically on their children when the children report idle. (#8052)

Bug Fixes

• client: Fix support for proxies when using grpc.NewClient so the target is resolved by the proxy as expected. (#7881)
  • Added WithLocalDNSResolution() dial option to explicitly force target resolution on the client instead. (#7881)
• weightedtarget: Return erroring picker when no targets are configured. (#8070)
• xds: Fail RPCs with UNAVAILABLE when the EDS resource is missing or contains no endpoints (#8070)
• xdsclient: Fix a bug where connectivity failures were reported to resource watchers before trying all listed servers. (#8075)
• grpc: Fix the number of bytes reported in the error message when encoded messages are larger than 4GB. (#8033)
• xds: Fixed a bug preventing tests from creating multiple servers or channels with different bootstrap configs. (#8050)
• grpc: Fix message length checks when compression is enabled and maxReceiveMessageSize is MaxInt (#7918)
  • Special Thanks: @​vinothkumarr227

Documentation

• client: Improve documentation of grpc.NewClient and ClientConn.CanonicalTarget by providing examples. (#8078)
• examples/features/dualstack: New example demonstrating usage of endpoints and dualstack functionality. (#8098)

Commits

• d01db5c Change version to 1.71.0 (#8105)
• 012f8bf xds: Enable dualstack flag (#8134)
• bf0c885 examples/features/dualstack: Demonstrate Dual Stack functionality (#8098) (#8...
• 05bdd66 ringhash: Remove TODO comment (#8096)
• ddb2484 xds: remove obsolete xDS transport custom dialer option (#8079)
• 8528f43 cleanup: replace Dial with NewClient (#7975)
• ae2a04f ringhash: Replace DNS resolver before sending xDS Update in test (#8091)
• e55819e lazy: Use channel to wait for resolver error being received in test (#8088)
• b524c08 xdsclient: include xds node ID in errors from the WatchResource API (#8093)
• 91eb6aa client: improve documentation of target strings (#8078)
• 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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[tekton-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please assign alangreene after the PR has been reviewed.
You can assign the PR to them by writing /assign @alangreene in a comment when ready.

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

[tekton-robot]

Hi @dependabot[bot]. Thanks for your PR.

I'm waiting for a tektoncd 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/test-infra repository.