fix(deps): Update dependency io.grpc:grpc-stub to v1.60.1

[cq-bot]

This PR contains the following updates:

Package	Type	Update	Change
io.grpc:grpc-stub	dependencies	minor	1.59.1 -> 1.60.1

---

Release Notes

grpc/grpc-java (io.grpc:grpc-stub)

v1.60.1

Bug Fixes

• util: Fix NPE when multiple addresses in an address group for petiole load balancer policies (#​10770)

v1.60.0

API Changes

• api: Stabilize ForwardingServerBuilder, ForwardingChannelBuilder2, and ForwardingChannelBuilder. Note that ForwardingChannelBuilder is stabilized (no changes will be made to it), but immediately deprecated in favor of ForwardingChannelBuilder2. (#​10586)
• api: Deprecate ForwardingChannelBuilder.delegate(). De facto this deprecates the class itself, since all classes extending ForwardingChannelBuilder implement the delegate() method. See javadoc for details (#​10587)
• api: Changed recently-introduced LoadBalancer.acceptResolvedAddresses() to return Status instead of boolean (#​10636). This is part of continued work to align the LB API cross-language and API stabilization
• stub: Deprecate StreamObservers (#​10654)
• alts: AltsChannelBuilder now extends ForwardingChannelBuilder2 (#​10587)
• protobuf: Stabilize ProtoUtils.metadataMarshaller() (#​10628)
• protobuf-lite: ProtoLiteUtils experimental comment (#​10627)

Behavior Changes

• core: ManagedChannels now check the address types provided by the nameResolver (for the given target) with the address types supported by the channel transport and generate an error in case of mismatch. That dramatically improves the error message when an issue occurs
• core: When a server stream is closed due to user's code (an uncaught exception in halfClosed, messagesAvailable, onReady callback of a ServerStream's listener), the Status.UNKNOWN returned to the client will have Application error processing RPC description. Previously the description was empty. This is helpful to differentiate between server errors originated in user application, gRPC library, or even those injected by a proxy. (#​10643)
• xds: Log ORCA UNIMPLEMENTED error to subchannel logger. This removes them from the normal application logs, reducing log spam

Improvements

• Change the underlying implementations of RingHash, RoundRobin, WeightedRoundRobin and LeastRequest load balancers to utilize the pick first load balancer rather than directly manage subchannels. This should only be noticeable if it introduced a bug
• core: Avoid flushing headers when the server returns a single response (#​9314). This is a performance optimization to reduce the number of packets for non-streaming responses
• util: Make grpc-core an implementation dependency. This will prevent the io.grpc.internal classes in grpc-core from being visible during compilation when depending on just grpc-util
• netty: Implement Http2Headers.isEmpty(). This fixes compatibility with Netty 4.1.101.Final.
• netty: Add NettyServerBuilder.maxRstFramesPerWindow(). This can be used to limit impact of Rapid Reset
• netty: Disable huffman coding in headers (#​10563). Huffman coding provides modest compression for relatively high CPU usage, especially within a data center. Rely just on the HPACK static and dynamic tables for compression, for higher performance. This only impacts header values 512 bytes or longer, as Netty already disabled Huffman for smaller values
• alts: Improve handshake failure error message by propagating original exception (#​10644)

Bug Fixes

• util: Remove shutdown subchannels from OD tracking (#​10683). This could have caused a memory leak on a long-lived channel. But we don’t think it could be triggered with our built-in load balancing policies.

Dependencies

• Bump Netty to 4.1.100.Final

Acknowledgements

@​anthonyjpratti
@​fedorka
@​jpd236
@​mateusazis
@​pkoenig10
@​yannickepstein
@​amirhadadi

---

Configuration

📅 Schedule: Branch creation - "before 4am on the first day of the month" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot.