MIRTH-1071
This was caused by ResultSetMetaData.getTableName() returning empty string. This happens for various cases in SQL Server and always happens for Postgres and Oracle. We decided to stop using table name in the element name at all and only use the alias/column name. If any conflicts happen we were throw an exception and stop the poll. The user will have to add a unique alias for the channel to process. By not checking against the table name anymore the message will no longer fail for columns of type TEXT.

MIRTH-2340
Since we will never be using table name in the result xml element names anymore, this issue is resolved. Note that for Postgres and Oracle, the table names were never used since the check of whether there were multiple tables would always return false.

MIRTH-3182
Fixed this by longer adding both the column name and column label to the result map. Also we now use the column label all the time instead of column name.
Created a class MirthCachedRowSet that extends CachedRowSetImpl which uses column label instead of column name when retrieving the column number from a string. This ensures that aliases will still work if the database driver correctly follows the JDBC4.0 spec to always return the column name with getColumnName(), and return the column name or alias with getColumnLabel() depending on if an alias was used. Currently it seems that of the drivers we currently provide, only MySQL follows this spec. The others all return the alias (if it exists) with either getColumnName() or getColumnLabel().
Issue: MIRTH-3124
MIRTH-3211: Fixed bug that caused sorting on the status columns to no longer work.
MIRTH-3163: Fixed bug with the new status retrieval that caused tags to not work correctly on the dashboard.
MIRTH-3203: The client no longer retrieves channel tags from the server at all. The Channels view and Dashboard view tags are now separate entities, and instead of requesting tags from the server, they are simply inferred from either the client-side channel status / dashboard status cache. The ChannelFilter dialog is no longer being kept around; it's now only instantiated as-needed and disposed afterwards.

The Client.getChannelTags method and the associated operation / servlet / controller code has been removed, since it is no longer necessary.