This will be called as a last resort if
#handleException(Throwable,RequestInfoForLogging) blew up
with a secondary unexpected exception while it was trying to handle the original exception.
IMPORTANT NOTE: THIS MUST ALWAYS RETURN A NON-NULL OBJECT AND MUST NEVER THROW AN EXCEPTION UNDER ANY
CIRCUMSTANCES!. If this blows up, then there is no more protection - you may get a raw framework error
response sent back to the caller with information leakage, stack traces, etc. It's highly recommended that this
method's implementation be as simple and bulletproof as possible, maybe even using a predefined return object
so that there's no possibility of failure (maybe with the
errorUid included in the response payload
using string replacement or something similarly bulletproof). It's also recommended that the return object
represent a basic HTTP status code 500 service error.