EDIT:

Circled back on the approach of adding a SentryRpcFilter :

• The error in the linked issue is not Sentry specific, but rather surfaced because we added a global exception filter in a hybrid application (http + microservices) – which means every rpc error reached our SentryGlobalFilter which then tried to handle RpcExceptions in a http manner. This is why we got this weird error.
• Instead I updated SentryGlobalFilter to more gracefully handle these scenarios and add a warning log that users should provide their own RrcException filter – will also update this in docs.

closes #16051