limithandler: Do not wrap errors from limithandler

In the limithandlers, we are returning structured errors so upstream clients can interpret that a request limit took place. However, we are currently swallowing these details by wrapping it in another gRPC error. Instead, just return this error without wrapping it, since the structured error already provides enough context as to why the error happened.

Changelog: changed