SQLCancel won't work in case of encrypted connection, and in some other cases

Current implementation does simple mysql_real_connect to open additional connection to kill the process at the server without any respect of other connection string options and connection attributes. e.g. if encryption is required, SQLCancel(and also SQLCancelHandle in 3.2 branch) will fail.
The fix should use minimal required subset of the usual driver connect routine.