Fix appsec int tests not actually running

[cataphract]

After upgrade to Gradle

Description

Reviewer checklist

• Test coverage seems ok.
• Appropriate labels assigned.

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 61.67%. Comparing base (575faf4) to head (d8e9485).
⚠️ Report is 29 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #3552      +/-   ##
==========================================
- Coverage   61.75%   61.67%   -0.08%     
==========================================
  Files         139      139              
  Lines       13051    13051              
  Branches     1712     1712              
==========================================
- Hits         8059     8049      -10     
- Misses       4228     4238      +10     
  Partials      764      764              

see 4 files with indirect coverage changes

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 575faf4...d8e9485. Read the comment docs.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[pr-commenter]

Benchmarks [ tracer ]

Benchmark execution time: 2025-12-31 12:50:23

Comparing candidate commit d8e9485 in PR branch glopes/fix-appsec-int-tests with baseline commit 575faf4 in branch master.

Found 2 performance improvements and 2 performance regressions! Performance is the same for 190 metrics, 0 unstable metrics.

scenario:ComposerTelemetryBench/benchTelemetryParsing

• 🟩 execution_time [-1357.325ns; -442.675ns] or [-11.803%; -3.849%]

scenario:MessagePackSerializationBench/benchMessagePackSerialization

• 🟥 execution_time [+2.361µs; +3.219µs] or [+2.242%; +3.058%]

scenario:MessagePackSerializationBench/benchMessagePackSerialization-opcache

• 🟥 execution_time [+12.558µs; +13.842µs] or [+12.421%; +13.692%]

scenario:TraceSerializationBench/benchSerializeTrace

• 🟩 execution_time [-33.841µs; -23.259µs] or [-7.539%; -5.182%]