Messages are now logged on channel startup if and only if messages are being recovered for a channel.

This is done by setting a boolean flag to determine if a logging message has already occurred and checking whether or not the dao returns messages to be recovered. If logging has not occurred and there are messages to recover, a log statement will be sent to the dashboard.

If at the end of the process the boolean flag was found to be true, a message will be written to the dashboard stating that the process has completed.

log4j properties were also modified to reflect info logging for the RecoveryTask
Issue: MIRTH-3179
Committed the correct version of log4j properties that changes the shutdown logging to undeploy.
Committed migration code to log recovery task properties.
Issue: MIRTH-3179
Added ability to inject map variables in the channel writer.

A metadata variable table was added to the channel writer which allows the user to input map keys, and a list was added to the VmDispatcherProperties to store the values from the table. The VmDispatcher attempts to replace each key by doing an ordered lookup across all maps. If the value is found, it is injected into the source map, otherwise it is ignored.
Issue: MIRTH-3380
Changed the description on the log4j migration to more generic.
Issue: MIRTH-3179
No longer creating the default truststore on startup. Removed truststore properties for new installations.
Issue: MIRTH-3414
Updated underlying source code variables to be more clear. Also added null checks for inserting variables from within the table.
Issue: MIRTH-3380
Added null checks to account for channel migration.
Issue: MIRTH-3380
Removed organization name from server settings.
Fixed a comment that was still referencing organization name.