Don't call LOGV2 in the boost logging exception handler

Since boost logging exceptions may occur during doLogImpl, this has the potential to re-enter doLogImpl, which is decidedly not reentry-safe. A couple of possible solutions:

• Add the log entry to a queue, which is popped by some forever-running handler thread.
• Don't log, and instead output the log message to stderr.