[Enhancement]: Honoring MSSQL aditional properties on connection url

Module

MSSQLServer

Proposal

Unlike the other database modules, the MSSQL module does not honor additional properties passed on the connection URL.

The culprit seems to be the 'parseUrl' method on the ConnectionUrl class. It expects the query parameters to be prefixed by the '?' character. However, in the MSSQL case, those parameters are preceded by the ';' character instead.

This is particularly troublesome when you use hibernate and the char/varchar datatypes. By default, the MSSQL driver uses Unicode encoding. This triggers full scans when querying by columns whose type is char/varchar. Eventually leading to deadlocks (I have a hunch that this issue is related to this).

I propose that we change the ConnectionUrl class to allow it to parse MSSQL URLs correctly. If you guys deem this change worthwhile, I can submit a PR for it.

Start with the ConnectionUrl class and its parseUrl method, then trace how the MSSQLServer module passes connection URLs and additional properties. Done means MSSQL URLs with semicolon-prefixed parameters are parsed and their additional properties are honored, with the behavior verified against the module's existing checks.