chore(rust): update weblog because of breaking changes

[paullegranddc]

Changes

• Change import path of the library
• Upgrade the PROD tag to the next 0.2.0
• Cleanup previous migration
• Disable rust in test-the-tests to prevent breakage until we release

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

[github-actions]

CODEOWNERS have been resolved as:

tests/test_the_test/test_compute_libraries_and_scenarios.py             @DataDog/system-tests-core
utils/build/docker/rust/install_ddtrace.sh                              @DataDog/apm-rust @DataDog/system-tests-core
utils/build/docker/rust/parametric/Cargo.lock                           @DataDog/apm-rust @DataDog/system-tests-core
utils/build/docker/rust/parametric/Cargo.toml                           @DataDog/apm-rust @DataDog/system-tests-core
utils/build/docker/rust/parametric/src/main.rs                          @DataDog/apm-rust @DataDog/system-tests-core
utils/scripts/compute_libraries_and_scenarios.py                        @DataDog/system-tests-core
utils/scripts/libraries_and_scenarios_rules.yml                         @DataDog/system-tests-core

[paullegranddc]

/merge

[dd-devflow-routing-codex]

View all feedbacks in Devflow UI.

2025-11-26 14:52:46 UTC ℹ️ Start processing command /merge

---

2025-11-26 14:52:50 UTC ℹ️ MergeQueue: waiting for PR to be ready

This pull request is not mergeable according to GitHub. Common reasons include pending required checks, missing approvals, or merge conflicts — but it could also be blocked by other repository rules or settings.
It will be added to the queue as soon as checks pass and/or get approvals.
Note: if you pushed new commits since the last approval, you may need additional approval.
You can remove it from the waiting list with /remove command.

---

2025-11-26 18:45:08 UTC ℹ️ MergeQueue: merge request added to the queue

The expected merge time in main is approximately 6m (p90).

---

2025-11-26 18:51:34 UTC ℹ️ MergeQueue: This merge request was merged