feat(error): provide service name on the client side of gRPC

[BugenZhao]

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.

What's changed and what's your intention?

In #13282, we introduced ServerError to be encoded inside the gRPC (HTTP) response and passed through the wire, so that the client could gain more information about the error occurred on the server. The most significant part is the service_name, so that we can know the target of the failing gRPC request.

However, [tonic::Status] is used for both client and server side. If there's something wrong with the server side and the error is directly created on the client side, the approach above is not applicable. In this case, the caller should set a "client side" service name to provide better error message. This is what this PR is for.

For example, run FLUSH after the meta node crashed:

ERROR:  Failed to run the query

Caused by these errors (recent errors listed first):
- 1: gRPC request failed: The service is currently unavailable
+ 1: gRPC request to meta service failed: The service is currently unavailable
  2: transport error
  3: error trying to connect
  4: tcp connect error
  5: Connection refused (os error 61)

We're able to know there's something wrong with the meta node in the error message.

Checklist

• I have written necessary rustdoc comments
• I have added necessary unit tests and integration tests
• All checks passed in ./risedev check (or alias, ./risedev c)

Documentation

• My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note

If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.

[BugenZhao]

I don't find a way to test it in CI (except for simulation test). May go to #14700 / #14438.

[yezizp2012]

LGTM

[xxchan]

If there's something wrong with the server side

In your example, what went wrong?

[BugenZhao]

If there's something wrong with the server side

In your example, what went wrong?

The meta node was killed and not reachable anymore.