[3.5] Upgrade gRPC-go to v1.52.0

[chaochn47]

Follow #16591 (comment) to upgrade dependency

This PR backports #14834 and #16324

This is a series of update with gRPC behavior changes auditing to eventually fix #16740

Please read https://github.com/etcd-io/etcd/blob/main/CONTRIBUTING.md#contribution-flow.

[chaochn47]

• https://github.com/grpc/grpc-go/releases/tag/v1.48.0
  • No breaking behavior changes
• https://github.com/grpc/grpc-go/releases/tag/v1.49.0
  • No breaking behavior changes
• https://github.com/grpc/grpc-go/releases/tag/v1.50.0
  • No breaking behavior changes
    • client: use proper "@" semantics for connecting to abstract unix sockets. (client: remove trailing null from unix abstract socket address grpc/grpc-go#5678)
      This is technically a bug fix; the result is that the address was including a trailing NULL byte, which it should not have. This may break users creating the socket in Go by prefixing a NULL instead of an "@", though, so calling it out as a behavior change.
    • etcd does not support abstract unix socket.
• https://github.com/grpc/grpc-go/releases/tag/v1.51.0
  • No breaking behavior changes
• https://github.com/grpc/grpc-go/releases/tag/v1.52.0
  • No breaking behavior changes
    • transport: ensure value of :authority header matches server name used in TLS handshake when the latter is overridden by the name resolver (transport: new stream with actual server name grpc/grpc-go#5748) breaks existing test cases.
    • However, etcd benefits from it to resolve etcd client v3 v3.5.0 sends invalid :authority header field value #13192 (comment) and Fix http2 authority header in multiple endpoints scenario and bump up grpc from v1.51.0 to v1.52.0 #16324 is backported to release-3.5.

[fuweid]

LGTM

[ahrtr]

LGTM

thx @chaochn47

[jmhbnz]

LGTM

[tjungblu]

/lgtm

well done @chaochn47 and thank you!