feat(er): Ensure APM_MULTICONFIG compat works

[tylfin]

Motivation

This is still in development for Java and Python here:

• add support for org level APM_TRACING configs dd-trace-java#9360
• chore(rc): apm tracing multi config support dd-trace-py#14364

But we want to have system-tests upfront to ensure it's functioning correctly for Sept releases.

Refs: DEBUG-4399, RFC here.

Changes

• Added service_name and env parameters to remote config command builders and senders in utils/_remote_config.py, allowing remote config commands to target specific services and environments. [1] [2] [3]
• Updated the config payload to include the service_target field, enabling precise control over which service and environment the configuration applies to.
• Added new test setup and assertions in Test_Debugger_InProduct_Enablement_Exception_Replay to verify exception replay enablement behavior when multiple remote config overrides are present, including service-level and wildcard targeting.
• Refactored helper methods in the test class to accept service and environment parameters, improving flexibility and reusability.
• Modified snapshot filtering logic to exclude snapshots created before the test start time, preventing cross-test interference when multiple tests share the same file.
• Updated send_rc_apm_tracing in utils.py to support the new service and environment parameters, ensuring all remote config commands can be properly targeted. [1] [2]
• Added a missing import for time to support timestamp-based filtering in tests.

Workflow

1. ⚠️ Create your PR as draft ⚠️
2. Work on you PR until the CI passes
3. Mark it as ready for review
   • Test logic is modified? -> Get a review from RFC owner.
   • Framework is modified, or non obvious usage of it -> get a review from R&P team

🚀 Once your PR is reviewed and the CI green, you can merge it!

🛟 #apm-shared-testing 🛟

Reviewer checklist

• If PR title starts with [<language>], double-check that only <language> is impacted by the change
• No system-tests internal is modified. Otherwise, I have the approval from R&P team
• A docker base image is modified?
  • the relevant build-XXX-image label is present
• A scenario is added (or removed)?
  • Get a review from R&P team

[cbeauchesne]

Framework usage : all good (even if test_inproduct_enablement_exception_replay_apm_multiconfig will be hard to debug, but there are some test design question that should be brainstormed)

I suggest toi get a review from someone familiar with the tested feature