fix: init storage before telemetry init

The telemetry initialization now takes a few seconds.
This delay is problematic for trace-to-profile correlation
since it delays the initialization of the process storage,
which the eBPF profiler checks once when it first encounters
the process.

* src/datadog/tracer.cpp

Author: elsa

src/datadog/tracer.cpp

@@ -71,6 +71,13 @@ Tracer::Tracer(const FinalizedTracerConfig& config,
       baggage_injection_enabled_(false),
       baggage_extraction_enabled_(false),
       correlate_full_host_profiles_(config.correlate_full_host_profiles) {
+#ifdef __linux__
+  // TODO: change the way this is done to handle programs that fork.
+  if (correlate_full_host_profiles_)
+    elastic_apm_profiling_correlation_process_storage_v1 =
+        *signature_.generate_process_correlation_storage();
+#endif
+
   telemetry::init(config.telemetry, logger_, config.http_client,
                   config.event_scheduler, config.agent_url);
   if (config.report_hostname) {
@@ -104,13 +111,6 @@ Tracer::Tracer(const FinalizedTracerConfig& config,
     }
   }
 
-#ifdef __linux__
-  // TODO: change the way this is done to handle programs that fork.
-  if (correlate_full_host_profiles_)
-    elastic_apm_profiling_correlation_process_storage_v1 =
-        *signature_.generate_process_correlation_storage();
-#endif
-
   if (config.log_on_startup) {
     logger_->log_startup([configuration = this->config()](std::ostream& log) {
       log << "DATADOG TRACER CONFIGURATION - " << configuration;