Fix CallWebhookJob behaviour when throwExceptionOnFailure is true

[cristian-fleischer]

Currently, the exceptions are not (re)thrown even if the CallWebhookJob::$throwExceptionOnFailure is set to true.
By adding the failed method and re-throwing the exception here if the flag is set to true this issue should be fixed.

[freekmurze]

Thanks!

[dovid]

I can't say for sure, but I believe this PR (and its subsequent release) is causing a bunch of 404 exception reports (in my sentry account) that have always failed silently until now. I haven't published the config file fwiw.

[freekmurze]

@dovid could you pinpoint your issue to a specific change here?

[dovid]

From what I understand, this PR fixed an issue where exceptions weren’t being thrown, even when throw_exception_on_failure was set to true. As a result, failures were silently ignored, and I had no visibility into them.

After our recent release, which included this update, we suddenly started seeing a flood of exceptions. At first, I was concerned that we had introduced a new issue. However, it turns out this behavior is expected—I just need to set throw_exception_on_failure to false if I don’t want to be notified of these failures.

So, technically, nothing is wrong; it was just a bit jarring to see so many exceptions all at once.