Monitor no longer passes log messages through log4j

The monitor in the 1.x series would take the log messages being passed to it from the tservers etc through it own log4j. This would allows us to capture that set of messages in a single monitor log. Since the updates in the 2.x series, this is no longer the case. It is very benificial for us to capture the aggregation of tserver messages being sent to the monitor in one log. All that is required is to relog the messages in the monitor. Perhaps the logger class can be TserverMessage, GcMessage, ManagerMessage, etc. to allow us to pipe those to separate logs if we wish.

Start by tracing how monitor-side handling receives TserverMessage, GcMessage, and ManagerMessage instances, then compare that flow with the 1.x behavior described in the issue. Confirm how the monitor currently logs these messages and determine how separate logger names could route them to distinct logs. Done means messages sent from tservers and other services are relogged by the monitor and can be captured together or separated by logger class.

Written by the indexing model from the issue text.