MIRTH-3327: Added null check for plugin properties to ChannelSetup when it checks for invalid ones during edit/import.
MIRTH-3306: Modified the HTTP Listener settings so that there are separate option groups for Parse Multipart and Include Metadata. Also added the same options on the HTTP Sender for the response content. The dispatcher now also always adds the status line and response headers into the connector map.
MIRTH-3324: Fixed the naming of the variables the TCP Listener places in the source map so that they make sense. Instead of "client" and "local", it is now "local" and "remote", and local _always_ refers to the local side of the connection, whether the TCP Listener is in client or server mode.
MIRTH-3331: The HTTP Listener now logs an error and dispatches an error event when it  fails to receive a message.
The order that plugins are loaded can now be set by adding a weight attribute to each serverClass or clientClass. If no weight is specified the plugin class will be given a default weight of 0. Plugins with greater weights will be loaded first. Weights can be negative. If multiple plugins have the same weight, the order they are loaded is random(although usually consistent)

Various plugins are also stored in a LinkedHashMap now rather than normal HashMap. Therefore when they are iterated through they will be in the order they were loaded. This allows us to determine the order for dashboard panel tabs, settings panel tabs, as well as other things. Certain types of plugins are not stored this way because they are typically iterated in alphabetical order. Data types are one example of this. Although they are not stored based on their weight, data type plugins will still be loaded based on them. 
Issue: MIRTH-3034
Reverting the changes from MIRTH-2945 that allows injecting the initial dashboard tab component. This is no longer necessary because the order of the tabs can now be set via plugin weights.
Issue: MIRTH-3034