fix(sidecar): use bare process_tags for RC Target to keep hash consistent

The `Target` struct in datadog-remote-config derives Hash over all
fields including process_tags. Both the sidecar (RC write side) and
the tracer (RC read side via ddog_remote_configs_service_env_change)
must agree on the Target hash, and the tracer passes the bare
process_tags Vec.

Augmenting only the sidecar side with svc.* via
`process_tags_with_svc_source()` made the Target hashes diverge,
orphaning RC configs in SHM (probes never installed, dynamic config
never applied).

For now revert this single call site to bare process_tags. A proper
follow-up should either exclude process_tags from Target's Hash/Eq
impl, or separate Target's identity fields from the payload metadata
fields. Trace + telemetry svc.* injection is unaffected.

Author: Leiyks

datadog-sidecar/src/service/runtime_info.rs

@@ -144,7 +144,10 @@ impl ActiveApplication {
             .expect("Expecting remote config invariants to be set early")
             .clone();
 
-        let process_tags = session.process_tags_with_svc_source();
+        // Target is hashed on the sidecar side and on the PHP read side
+        // (sidecar.c:ddog_remote_configs_service_env_change). PHP passes the
+        // bare process_tags Vec, so we must too — otherwise SHM lookups miss.
+        let process_tags = session.process_tags.lock_or_panic().clone();
 
         if *session.remote_config_enabled.lock_or_panic() {
             self.remote_config_guard = Some(