Add try/catch around handle_message() to catch errors during logging.

[NHDaly]

Fixes #56889.

Before this PR, an exception thrown while constructing the objects to log (the msg) would be caught and logged. However, an exception thrown while printing the msg to an IO would not be caught, and can abort the program. This breaks the promise that enabling verbose debug logging shouldn't introduce new crashes.

After this PR, an exception thrown during handle_message is caught and logged, just like an exception during msg construction:

julia> struct Foo end

julia> Base.show(::IO, ::Foo) = error("oh no")

julia> begin
           # Unexpectedly, the execption thrown while printing `Foo()` escapes
           @info Foo()
           # So we never reach this line! :'(
           println("~~~~~ ALL DONE ~~~~~~~~")
       end
┌ Error: Exception while generating log record in module Main at REPL[10]:3
│   exception =
│    oh no
│    Stacktrace:
│      [1] error(s::String)
│        @ Base ./error.jl:44
│      [2] show(::IOBuffer, ::Foo)
│        @ Main ./REPL[9]:1
...
│     [30] repl_main
│        @ ./client.jl:593 [inlined]
│     [31] _start()
│        @ Base ./client.jl:568
└ @ Main REPL[10]:3
~~~~~ ALL DONE ~~~~~~~~

This PR respects the change made in #36600 to keep the codegen as small as possible, by putting the new try/catch into a no-inlined function, so that we don't have to introduce a new try/catch in the macro-generated code body.

[IanButterworth]

I think this wold mean try-catch in every log macro usage? That would make #52533 a lot worse (but at least it'd be consistent!)

cc. @gbaraldi

[gbaraldi]

Logging already introduces try catches in places so I'm not sure how much worse it can get 😄. Notably for GPU stuff I believe we are going in the way of doing more RAII like things to not rely on the GC as much

[NHDaly]

Yeah, exactly. I think that since it's already adding try/catches in so many places, we may as well be consistent in applying them to all parts of the logging process.

[IanButterworth]

It just elevates the need to fix that issue. 👍