chore: coverage job suggests maybe we need the coverage cfg actually

Author: apiarian-datadog

ddcommon/src/connector/mod.rs

@@ -97,7 +97,7 @@ mod https {
     /// happens here.  On non-unix platforms, ddcommon uses `ring` instead, which handles this
     /// at rustls initialization. TODO: Move to the more ergonomic LazyLock when MSRV is 1.80
     /// In fips mode we expect someone to have done this already.
-    #[cfg(any(not(feature = "fips"), test))]
+    #[cfg(any(not(feature = "fips"), coverage))]
     fn ensure_crypto_provider_initialized() {
         use std::sync::OnceLock;
         static INIT_CRYPTO_PROVIDER: OnceLock<()> = OnceLock::new();
@@ -112,7 +112,7 @@ mod https {
 
     // This this actually needs to be done by the user somewhere in their own main.
     // This will only be active on Unix platforms
-    #[cfg(all(feature = "fips", not(test)))]
+    #[cfg(all(feature = "fips", not(coverage)))]
     fn ensure_crypto_provider_initialized() {
         compile_error!("is this what we are trying to compile in coverage?");
     }