When uncaught exceptions are handled by ErrorHandler::handleException(), that method logs them, then calls a callback to let the app know about the exception itself.

This causes two issues:

1. that log happens without context, which leads to excluded_http_codes not working as intended for http errors thrown inside the callback of a StreamedResponse #57902
2. logs are duplicated: one by ErrorHandler, twice by the callback

In this PR, I propose to consider that if terminateWithException is configured as a callback, we assume that the app will handle the logging on its own.

Tested in practice, this works nicely.

Adding a test case is quite complex as all this involves many pieces and global state, so I skipped adding one.