Feat: Log dumper

[waldgange]

Introduce a set of parameters for log record dumping by a trigger message. This section can be added to the Broker config:

{
    ....
    "taskConfig": {
        ...
        "logDump": {
            "recordBufferSize": 32768,
            "recordingLevel": "TRACE",
            "triggerLevel": "FATAL"
        }
        ....
    }
    ....
}

Where:
recordBufferSize is a size of default logger's record buffer in bytes.
recordingLevel is the lowest severity level of the record that will be stored by the logger in its log record buffer.
triggerLevel is the lowest severity level of the record that will cause immediate publication of that record and any records in the logger's log record buffer.

[bmq-oss-ci]

Build 294 of commit 004c2fc has completed with FAILURE

[bmq-oss-ci]

Build 298 of commit 28ec79b has completed with FAILURE

[bmq-oss-ci]

Build 300 of commit 8ce4504 has completed with FAILURE

[chrisbeard]

Looks like there's a unit test for the log controller, let's extend that to test this as well.

I think the most important thing to make sure of with this test is that we don't break compatibility with older configs that don't utilize this.

[waldgange]

@chrisbeard I've added a unit test for LogControllerConfig::fromObj(), also I've removed the outdated method fromDatum() and its unit test.
In order not to break compatibility with old broker configs we have to release this feature in two steps. As the first step we release the new config, containing the new parameters. When all machines upgrade to this version we will release the broker that retrieves new parameters from the config

[bmq-oss-ci]

Build 310 of commit a63f4e7 has completed with FAILURE

[bmq-oss-ci]

Build 351 of commit 7b9f24e has completed with FAILURE

[bmq-oss-ci]

Build 358 of commit f645c26 has completed with FAILURE

[bmq-oss-ci]

Build 360 of commit c3ef08d has completed with FAILURE