ci: disable appsec_iast_tdd_propagation suite temporarily

[gnufede]

CI: Disables IAST TDD Propagation suite while the fix to the proper issue is done

Checklist

• Change(s) are motivated and described in the PR description
• Testing strategy is described if automated tests are not included in the PR
• Risks are described (performance impact, potential for breakage, maintainability)
• Change is maintainable (easy to change, telemetry, documentation)
• Library release note guidelines are followed or label changelog/no-changelog is set
• Documentation is included (in-code, generated user docs, public corp docs)
• Backport labels are set (if applicable)
• If this PR changes the public interface, I've notified @DataDog/apm-tees.

Reviewer Checklist

• Title is accurate
• All changes are related to the pull request's stated goal
• Description motivates each change
• Avoids breaking API changes
• Testing strategy adequately addresses listed risks
• Change is maintainable (easy to change, telemetry, documentation)
• Release note makes sense to a user of the library
• Author has acknowledged and discussed the performance implications of this PR as reported in the benchmarks PR comment
• Backport labels are set in a manner that is consistent with the release branch maintenance policy

[datadog-dd-trace-py-rkomorn]

Datadog Report

Branch report: gnufede/temp-disable-suite
Commit report: d270a12
Test service: dd-trace-py

✅ 0 Failed, 121260 Passed, 51608 Skipped, 9h 4m 13.55s Total duration (2h 46m 33.58s time saved)

[pr-commenter]

Benchmarks

Benchmark execution time: 2024-04-05 11:29:45

Comparing candidate commit d270a12 in PR branch gnufede/temp-disable-suite with baseline commit 918aeba in branch main.

Found 3 performance improvements and 1 performance regressions! Performance is the same for 187 metrics, 9 unstable metrics.

scenario:sethttpmeta-collectipvariant_exists

• 🟥 max_rss_usage [+579.217KB; +807.689KB] or [+2.696%; +3.759%]

scenario:sethttpmeta-obfuscation-no-query

• 🟩 max_rss_usage [-674.385KB; -514.683KB] or [-3.035%; -2.316%]

scenario:sethttpmeta-obfuscation-worst-case-explicit-query

• 🟩 max_rss_usage [-914.532KB; -551.017KB] or [-4.099%; -2.470%]

scenario:sethttpmeta-useragentvariant_not_exists_1

• 🟩 max_rss_usage [-752.780KB; -544.014KB] or [-3.402%; -2.458%]

[github-actions]

The backport to 2.6 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-2.6 2.6
# Navigate to the new working tree
cd .worktrees/backport-2.6
# Create a new branch
git switch --create backport-8883-to-2.6
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 672831c2aa257610e3c5fdd15e80d7c20465b713
# Push it to GitHub
git push --set-upstream origin backport-8883-to-2.6
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.6

Then, create a pull request where the base branch is 2.6 and the compare/head branch is backport-8883-to-2.6.