Fix TLS MSSQL test in FIPS-enabled environment and disable non-TLS MSSQL tests in FIPS-enabled environment

[michalvavrik]

Summary

Looks like secured communication is required and cannot be disabled in MSSQL JDBC driver by no means I had tried based on https://learn.microsoft.com/en-us/sql/connect/jdbc/fips-mode?view=sql-server-ver16 (no, FIPS property doesn't work). I have tried several providers including SunPKCS11 with RH OpenJDK 17/21 and BouncyCastle FIPS, but only provider that did the trick for MSSQL JDBC driver was BouncyCastle JSSE FIPS. However this provide is not native compatible as documented here https://quarkus.io/guides/security-customization#bouncy-castle-jsse-fips (I tried it, doesn't work). So what this PR does:

• we have one TLS MSSQL test, that is migrated to BC JSSE FIPS so that we test MSSQL in FIPS-enabled environment
• remaining MSSQL tests that doesn't use secured communication are disabled in FIPS as native is more important

Note: I tried to migrate all the SQL Server tests to the BC JSSE FIPS and it works.

Please select the relevant options.

• Bug fix (non-breaking change which fixes an issue)
• Dependency update
• Refactoring
• Backport
• New scenario (non-breaking change which adds functionality)
• This change requires a documentation update
• This change requires execution against OCP (use run tests phrase in comment)

Checklist:

• Methods and classes used in PR scenarios are meaningful
• Commits are well encapsulated and follow the best practices

[gtroitsk]

LGTM