Test | Addressing Net5 runtime issues

[JRahnama]

While trying to test the driver against Net5, runtime caught some unobserved issues/warnings

1. Classes implementing IDisposable should dispose all related fields.
2. Re-Throwing caught exception from catch block will change the stack, hence should not be done.
3. Calling overridable methods from constructions are prohibited.
4. Raising exception from unexpected places such as dispose is not recommended.
5. BinaryFormatter is not safe and should not be used in all versions of .NETFramework and netcoreapp 2.1 and upper versions.
6. Warning CA1416: Platform compatibility this issue came up for tests running on Windows for CspParameters class. In net5.0 and later versions OperatindSystem.IsWindows
   is introduced to get the operating system but the API is not known in lower versions.

In some cases such as overridable methods usage I have moved the method inside a concrete method and called it from there and that made the driver to compile and run. I am eager to hear all comments about the changes to improve them and make them better.

Thanks

Update:

I noticed some improvement opportunities in our test lab:

SqlNotificationTest was using ManualResetEvent I have changed them to use ManualResetEventSlim. Reasoning to do so:

1. ManualResetEventSlim is less expensive than ManualResetEvent.
2. ManualResetEventSlim is fully managed version of its predecessor.

there are small differences such as kernel related behavior and blocking the thread which may have better effect on our test lab.

[Wraith2]

Tiny suggestions otherwise LGTM.

[cheenamalhotra]

/azp run CI-Ub16-SQL17L-TR, CI-Win10-AzureSQLDB, CI-Win10-SQL17W, CI-Win10-SQL19W-Fx48-Core31, CI-Win10-SQL19W-ManagedSNI, CI-Win10-SQL19W-TR

[azure-pipelines]

Azure Pipelines successfully started running 6 pipeline(s).