Reactive MSSQL client needs additional test coverage using encrypted communication so that we can support it in FIPS-enabled environment

[michalvavrik]

I have disabled SQL Server test coverage in FIPS-enabled environment as it didn't work #2097. I tried to migrate it using BouncyCastle JSSE FIPS security provider and it worked, but it would require to disable native and I think it should be unnecessary considering that this extension is not using blocking JDBC driver, I think SunPKCS11-NSS-FIPS should work there and that is preferred security provider with RH OpenJDK ATM.