Completely overhauled the backend for the Message Browser. We are no longer using any type of array/list aggregate functions from various databases. This also means that we can now support many older versions of our backend databases. Searches are no longer done in a single query regardless of how many messages are in the channel. Now the searches/deletes/reprocessing/count are all done in batches than scan based on ranges of message Ids. This means that there is a cap on the amount of memory a search will use. This prevents text searches on channels with large amounts of messages from using up all the memory on a machine and slowing down or crashing the whole system. Searches now occur in linear time regardless of how many messages are in a channel. The performance for non-text searches has decreased slightly but are still within usable ranges, while text/custom metadata/content searches have improved dramatically.

deleting/reprocessing/counting have all been overhauled as well to use the new pattern. 

Text search no longer adds all the content types to the content type search

Removed messageIdUpper and messageIdLower from the message filter. Now we are using maxMessageId and minMessageId instead.

Removed source and type from MessageFilter because they are no longer used

MIRTH-3191
MIRTH-3216
Updated the data pruner to use the ListRangeIterator 
Issue: MIRTH-3147
Now allowing content searching on all content types since text search also searches all content types now.

Removed some debug code from DonkeyMessageController.
Issue: MIRTH-3123