SNOW-844477: Allow connection property CLIENT_OUT_OF_BAND_TELEMETRY_ENABLED to disable OOB telemetry

[sfc-gh-ext-simba-lb]

Overview

SNOW-844477

Out-of-band telemetry is enabled by default in the driver until a session is opened and the session properties are read. If CLIENT_OUT_OF_BAND_TELEMETRY_ENABLED is disabled on the account level and returned in the session properties, the telemetry will then be disabled. But since it is enabled before connection, if there are OCSP exceptions they will send telemetry requests.

External contributors - please answer these questions before submitting a pull request. Thanks!

Please answer these questions before submitting your pull requests. Thanks!

1. What GitHub issue is this PR addressing? Make sure that there is an accompanying issue to your PR.

https://github.com/snowflakedb/snowflake-sdks-drivers-issues-teamwork/issues/478

2. Fill out the following pre-review checklist:

   • I am adding a new automated test(s) to verify correctness of my new code
   • I am adding new logging messages
   • I am modifying authorization mechanisms
   • I am adding new credentials
   • I am modifying OCSP code
   • I am adding a new dependency

3. Please describe how your code solves the related issue.

   To allow CLIENT_OUT_OF_BAND_TELEMETRY_ENABLED connection property to control if OOB telemetry is enabled or not. This can still be overridden by session properties later in the login flow. Part 2 will be on the server side to allow telemetry session properties to be configured by the user on the account level.

Pre-review checklist

• This change has passed precommit
• I have reviewed code coverage report for my PR in (Sonarqube)

[sonarqubemergegate]

SonarQube Quality Gate

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[sfc-gh-mknister]

LGTM! Just had 1 clarification- did you get a chance to manually check that no OCSP OOB messages could get sent before SFSession.open() gets called? If so, this looks good.