Bump grpc.version from 1.82.1 to 1.82.2 in /lang/java

[dependabot]

Bumps grpc.version from 1.82.1 to 1.82.2.
Updates io.grpc:grpc-core from 1.82.1 to 1.82.2

Release notes

Sourced from io.grpc:grpc-core's releases.

v1.82.2

• Revert "xds: reuse connections to the control plane across channels" added in 1.81.0 (#12886). If using xds heavily with many targets, then MAX_CONCURRENT_STREAMS to the control plane could be exceeded. This then prevents loading resources for new targets, which causes those channels to hang on name resolution. RPCs would see the nondescript "DEADLINE_EXCEEDED: Deadline Context was exceeded after Xs" or "DEADLINE_EXCEEDED: Deadline CallOptions was exceeded after Xs"

Commits

• 86780d3 Bump version to 1.82.2
• f865ab7 Update README etc to reference 1.82.2
• 00ff5e5 Revert "xds: reuse GrpcXdsTransport and underlying gRPC channel to the same x...
• 5be5f4c Bump version to 1.82.2-SNAPSHOT
• See full diff in compare view

Updates io.grpc:grpc-stub from 1.82.1 to 1.82.2

Release notes

Sourced from io.grpc:grpc-stub's releases.

v1.82.2

• Revert "xds: reuse connections to the control plane across channels" added in 1.81.0 (#12886). If using xds heavily with many targets, then MAX_CONCURRENT_STREAMS to the control plane could be exceeded. This then prevents loading resources for new targets, which causes those channels to hang on name resolution. RPCs would see the nondescript "DEADLINE_EXCEEDED: Deadline Context was exceeded after Xs" or "DEADLINE_EXCEEDED: Deadline CallOptions was exceeded after Xs"

Commits

• 86780d3 Bump version to 1.82.2
• f865ab7 Update README etc to reference 1.82.2
• 00ff5e5 Revert "xds: reuse GrpcXdsTransport and underlying gRPC channel to the same x...
• 5be5f4c Bump version to 1.82.2-SNAPSHOT
• See full diff in compare view

Updates io.grpc:grpc-netty from 1.82.1 to 1.82.2

Release notes

Sourced from io.grpc:grpc-netty's releases.

v1.82.2

• Revert "xds: reuse connections to the control plane across channels" added in 1.81.0 (#12886). If using xds heavily with many targets, then MAX_CONCURRENT_STREAMS to the control plane could be exceeded. This then prevents loading resources for new targets, which causes those channels to hang on name resolution. RPCs would see the nondescript "DEADLINE_EXCEEDED: Deadline Context was exceeded after Xs" or "DEADLINE_EXCEEDED: Deadline CallOptions was exceeded after Xs"

Commits

• 86780d3 Bump version to 1.82.2
• f865ab7 Update README etc to reference 1.82.2
• 00ff5e5 Revert "xds: reuse GrpcXdsTransport and underlying gRPC channel to the same x...
• 5be5f4c Bump version to 1.82.2-SNAPSHOT
• See full diff 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 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)