gRPCurl functionality to support HTTP/3 (QUIC), as the underlying transport mechanism.

If a given system uses the newly support HTTP/3 channel configuration then gRPCurl's current TCP only implementation can not provide any usefulness.

The solution is for gRPCurl's gRPC functionality to support HTTP/3 (QUIC), as the underlying transport mechanism.

Alternatives: None.

What is HTTP/3 and why is support important?
https://devblogs.microsoft.com/dotnet/http-3-support-in-dotnet-6/#what-is-http-3-and-why-is-support-important

gRPC with HTTP/3
https://devblogs.microsoft.com/dotnet/http-3-support-in-dotnet-6/#grpc-with-http-3

Github: grpc/grpc
grpc/grpc#19126
grpc/proposal#256
https://github.com/JamesNK/proposal/blob/jamesnk/http3/G2-http3-protocol.md

Start by reviewing grpc/grpc#19126 and the linked HTTP/3 protocol proposal to understand the required gRPC transport behavior. Then inspect grpcurl's current TCP-based gRPC path and determine how HTTP/3 (QUIC) would integrate. Done means grpcurl can use an HTTP/3 channel configuration to interact with gRPC servers.

Written by the indexing model from the issue text.