Logger Refactor

[qoire]

logback.xml and logback in general provides excellent facilities for doing a variety of things users might want from a logging perspective. For example, for one of our internal projects:

• We block logging from certain modules, and certain class paths
• We direct logging output to multiple appenders (ex. Email, Database, Log)
• We modifying the format of output we get
• We override default logging with our own logback.xml file easily.

These are features that will let the (experienced) user self-diagnose their system, as well as integrate with any production pipelines that they might have, currently we do this from an OS level but logback can do the same thing for us (and better!).

I would strongly recommend:

• Refactoring our current logging facilities and tie it directly with an implementation.
• Reduce the awkwardness of how we initialize our logging, currently it's done via a convoluted static initialization process.
• Rethink how we separate between different loggers. (For example, class tied to VM or GENERAL might be very noisy, if we give it some identifier, we can disable it individually.)

Also: if someone is working on loggers for production, we might want to consider include #651 as a dependency.