system-tests improvments: simpler CI definition; Report to test optimization

[cbeauchesne]

What does this PR do?

It achieves two tasks :

• Runs all existing weblogs on tracer_release scenario group:
  October 9th, a new version of the WAF has been pushed to dd-trace-rb. Turns out that this version was not passing a test (APPSEC-59579). But dd-trace-rb CI was running this test against the weblog rails70, which was removed at this time, so the issue was not seen during the PR. It showed that running a subset of scenarios/weblog is prone to errors like that, wihtout mentionning that it adds some maintenance on this list.
  -> By using tracer_release, the scenario and weblog list is delegated to system-tests, keeping the maintenance level to its minimum here. If for some reason set of scenario/weblog shall not be run, it will be addressed directly in system-tests.
• Push test runs to Test Optimization

CI impact : the current pipeline takes ~16'30

The new pipeline :

• run 1 : 18'40 (expected failure, I forgot to add a secret)
• run 2 : 18'53

Change log entry
None.

Additional Notes:

How to test the change?

[github-actions]

Thank you for updating Change log entry section 👏

^{Visited at: 2025-10-23 14:58:49 UTC}

[datadog-official]

✅ Tests

🎉 All green!

❄️ No new flaky tests detected
🧪 All tests passed

🎯 Code Coverage
• Patch Coverage: 100.00%
• Total Coverage: 98.58% (+0.01%)

View detailed report

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: dcd1c3a | Docs | Was this helpful? Give us feedback!}

[y9v]

awesome! thanks