Fixed database receiver connector so that it behaves the same was as it did in 2.x by converting the result map keys to lowercase.

Also fixed the behavior of referencing variables in the variable list so that it is case-insensitive, as it was in 2.x.
Issue: MIRTH-2983
Fixed problem with database receiver UI. When the select query selected quoted column names, the quotes were being included when creating variable names for the columns in the variable list.
Issue: MIRTH-2990
Removed database connection info in the database connector unit tests that was accidentally committed.
Issue: MIRTH-2320
Removed username/password information that was accidentally committed with the JMS receiver unit tests.
Issue: MIRTH-1945
MIRTH-2979: Split up socket creation and connection so that they can be forcibly halted if need be. The TcpDispatcher's onStop() method now only needs to dispose of send timeout threads, because the thread itself will close the associated socket if it's interrupted when the connector is stopped/halted.

MIRTH-2986: Updated references from TcpUtil.parseInt to NumberUtils.toInt, and removed parseInt from TcpUtil.

MIRTH-2993: The HaltTask now waits for all dispatch threads to finish, and also waits for the channel executor to terminate (includes the recovery task and chain tasks). After the HaltTask returns, there should be no lingering threads stuck in message processing. The destination connector also does its part by joining on all queue threads before returning from halt().
Modified the values returned by ConfigurationController.getStatus().

STATUS_OK (0) now indicates that the full server startup sequence has completed, rather than merely the messaging engine startup.

STATUS_INITIAL_DEPLOY (3) has been added to indicate that the initial deploy all channels operation is in progress.
Issue: MIRTH-2992
Fixed global post-processor so that the 'response' variable placed into the scope is null if the channel post-processor returned a null/undefined response. Previously, it was creating a userutil Response object wrapped around a null Donkey response object, which would result in a NPE when the global post-processor was executed.
Issue: MIRTH-2966