…ft#74)

* Add connection properties to specify a custom TrustManager

Adds two new connection properties that can be used to specify a custom
TrustManager implementation:

trustManagerClass - Class name of the custom TrustManager

trustManagerConstructorArg - Optional argument to pass to the constructor
constructor of the custom TrustManager.

If encryption is enabled and the trustManagerClass property is specified,
it will be retrieved via Class.forName(...).

If the optional property trustManagerConstructorArg is specified, then a
constructor will be retrieved via getDeclaredConstructors(String.class).
The TrustManager will then be instantiated by specified the optional
argument as a parameter.

If the optional property trustManagerConstructorArg is not specfied,
then the default no argument constructor of the class will be retrieved
and instantiated.

* Adding a few simple test to verify the newly added connection properties

* Rename custom trustmanager test package name

Previous package name used camel case. Corrects naming to be lower case.

* Add missing newlines to trustmanager test classes

* Refactor references to trust managers in tests

* Refactor whitespace and unneeded extends Object

* Add resource cleanup to trust manager tests

* Refactor failure handling for trust manager test

* Rename tmClazz to tmClass

* Add new trust manager properties to SQLServerDataSource

* Reword comment

* Format custom trustmanager changes with auto formatter

Fix exception thrown by getters on null columns

removing javax.xml.bind package dependency

fix methods that use sp_fkeys

Cleanup travis appveyor

Fix for Classloader leak issue

Remove explicit extends object

Remove redundant if/else statements

Remove unnecessary return statements

…ressions

Simplify overly complex boolean expressions

…APIs

Removing deprecated APIs in java 9

…nverter

Revert "removing javax.xml.bind package dependency "

…_deprecated_APIs

Revert "Removing deprecated APIs in java 9"

Replace manual array copying with System.arraycopy().

Calling toString() on a String object is redundant

Replace bare literals with magic constants. For example:

`cal.set(1, 1, 577738, 0, 0, 0);`

becomes

`cal.set(1, Calendar.FEBRUARY, 577738, 0, 0, 0);`

…if-statement

Revert "Remove redundant if/else statements"

…tryLogic

Update Appveyor for jdk9

Re-introduce Retry logic for prepared statement caching

…pare to class level declaration to avoid multi-threading issues.

Added needsPrepare Check and removed error code 99586 check

Update changelog and driver version for RTW 6.4 release

Update SNAPSHOT for upcoming preview release.

dev to connres