Add option to configure max received message size for jaeger-query

[SOF3]

Currently this option only exists for collector but not for query.

This option is required when a storage returns a very large grpc message (>4MiB).

Which problem is this PR solving?

• Resolves [Bug]: HTTP Error: grpc stream error: rpc error: code = ResourceExhausted desc = grpc: received message larger than max (7833328 vs. 4194304) #4350

Short description of the changes

• Add a --grpc-storage.max-recv-msg-size option.

[ChillOrb]

@SOF3 What if someone wants to set it as -1 (no limit) ref?

[SOF3]

@ChillOrb the argument interpretation is copied from the equivalent option in collector --collector.grpc-server.max-message-size. It is also > 0 there.

[ChillOrb]

Looking at this a bit more, I found that currently grpc-go only supports MaxRecvMsgSize and not something like MaxRecvMsgLength(which is a valid option link) so for linkthe condition > 0 makes sense.

As for the following variable nameflagSuffixGRPCMaxReceiveMessageLength which is accepted from "max-message-size" link I feel this should instead be called flagSuffixGRPCMaxReceiveMessageSize since MaxMessageLength has a different meaning in grpc terms and can be set as -1 and thus should not have > 0 condition.

@yurishkuro What do you think?

@SOF3 What if someone wants to set it as -1 (no limit) ref?

[yurishkuro]

Go API calls is "size", which is what we call it too. "length" is from some other documentation.

[yurishkuro]

any follow-up?

[SOF3]

Rewrote the commit, changing the grpc storage instad of the query command.

[yurishkuro]

please add to tests