report suppressed MessageBuilder exceptions to the service

[jakecoffman]

Code improvement description

In #9560 I started printing the suppressed exception, however it would be best to also report it to Sentry so we can see when we introduce regressions.

Due to the architecture of command and updater, this is a bit tricky.

One way that just occurred to me is to store those exceptions in an array of errors on the MessageBuilder, and have the updater check that array for entries and report them to Sentry after the MessageBuilder runs.

[jurre]

@jakecoffman I think something like this could do the trick? It's a bit more generic than storing it on the MessageBuilder and this way we can reuse it across all of core where we might run into a similar situation where we don't want to raise on errors, but we do want to report them to Sentry

#9601

[Nishnha]

I updated #9601 and it's passing CI now. How would we go about testing + releasing this?