[Enhancement]: Return rate limit details when returning grpc RESOURCE_EXHAUSTED code

[samlaf]

Use case and current behavior

Currently our disperser only returns a grpc RESOURCE_EXHAUSTED error, see for eg here.

However, this error code is returned for many different errors, including by the grpc framework itself:

Enhancement

We should add status details (see for eg https://jbrandhorst.com/post/grpc-errors/) so that clients can uniquely identify that they are being rate limited. We could also consider (if this information is available) returning as part of the details an approximate suggested amount of time that the client should wait before retrying in order to clear the rate limit.

Solution proposal

No response

Additional Information

No response