Fix MSSQL tests in FIPS-enabled environment

[michalvavrik]

Summary

MSSQL JDBC driver doesn't allow unsecured communication in FIPS-enabled environment no matter of what properties I set. So migrating most of the tests to TLS and leaving few tests with unsecured communication.

I run fixed tests on FIPS, but I didn't run other tests that could theoretically be affected by changes here, so I'll have to test that before I request review.

Please select the relevant options.

• [x] 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:

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

[michalvavrik]

I'll close this temporarily because I don't want to run CI everytime I push changes to my FIPS env. anyway, this would have nasty native impacts as BCFIPSJSSE provider option is currently not supported in native image.