Updated derby jar in Donkey to use the same version that's in the Server: 10.10.1.1
Issue: MIRTH-2706
MIRTH-2334, MIRTH-2797: Added back the source/type/version as default custom metadata columns.

A populateMetaData method has been added to XmlSerializer which is used in the FilterTransformerExecutor to extract metadata and place it in the connector map. Some data types place metadata in the map, some don't (like DICOM or Raw). In the Administrator, we add the Source and Type columns by default when creating a new channel. The user can specify which columns show up by default in the server settings.

The getMetadataFromDocument method in IXMLSerializer has been replaced with getMetaDataForTree. This method gets metadata that should be shown in the message template tree. Sometimes it's the same information (like HL7 v2.x), sometimes it's not (like XML).

The default metadata columns are stored in ServerSettings as a List, so that we can easily migrate to a more complex column table later on. The default core property is *not* stored in the database upon creation or migration, so if a user installs 3.0, never saves the server settings, and upgrades to a later version in which we've updated the default columns, their installation would then have the newly updated columns, instead of preserving the 3.0 defaults (source and type).

Quick parsing (getMetadataFromEncoded) really only existed for ER7 in 2.x. EDI/X12/NCPDP implemented the method, but actually just serialized the data and called getMetadataFromDocument instead. So even if there wasn't an active transformer, the message was still being serialized. Now there is quick metadata parsing for both EDI/X12 and NCPDP. Also, the quick parsing in ER7Serializer has been rewritten to be more efficient.

The MessageObject and ValueReplacerConnectorMessage userutil objects have been updated so that the deprecated methods now work (even though they're still deprecated).