How InvokeMethodGrpcAsync Passes Request Headers More Elegantly

## Ask your question here

If InvokeMethodGrpcAsync is used, the requests from service A -> sidecar and sidecar -> B should be gRpc communication, but currently InvokeMethodGrpcAsync does not provide custom Headers, I saw a similar problem: [#852](https://github.com/dapr/dotnet-sdk/issues/852), through [CreateInvocationInvoker](https://github.com/dapr/dotnet-sdk/blob/master/src/Dapr.Client/DaprClient.cs#L133) can Doing custom Haeaders, but is this too much trouble, which means InvokeMethodGrpcAsync is completely useless for me?