If there is an error in generated code, Quarkus might choke super early in the lifecycle when the logging configuration has yet to be applied. In this case, we need to at least set up a ConsoleHandler that will print the exception

P.S. This was first encountered by @iocanel when doing some deep experimentation on CLI plugins