[CLIENT-3160] Enable TLS when deploying an enterprise edition server for testing

[juliannguyen4]

We enable TLS standard authentication to verify that the OpenSSL library bundled with the wheel works. You can manually verify this by enabling debug logging in the client while running the tests, and checking that the server certificate was verified in the logs

Regression testing

• [x] Massif shows a few MB more memory is being used but no other strange behavior
• [x] Build artifacts passes except noise
• [x] Valgrind shows no memory errors. There are memory leaks found from enabling TLS but we can address them later.
• [x] Check that there is no significant performance impact when using TLS. Test this by running the slowest tests with and without TLS. Valgrind on dev takes 1h3m and this branch takes 1h4m

In run-ee-server composite action:

1. Generate self-signed CA certificate (public key) and private "decrypting" key
2. Build the server image with TLS enabled. In Dockerfile, server will use the same CA certificate (public key) + CA private key from step 1 to sign (encrypt) and create its own server certificate
3. Configure tests to confirm the server's identity by checking that the CA certificate from step 1 did sign the server certificate from step 2a

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 80.89%. Comparing base (8d941e5) to head (e145097). Report is 1 commits behind head on dev.

Additional details and impacted files

```diff @@ Coverage Diff @@ ## dev #692 +/- ## ========================================== + Coverage 80.77% 80.89% +0.11% ========================================== Files 102 102 Lines 15185 15186 +1 ========================================== + Hits 12266 12285 +19 + Misses 2919 2901 -18 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

---

🚨 Try these New Features:

• Flaky Tests Detection - Detect and resolve failed and flaky tests