fix(asm): remove datadog.api_security metrics

[christophe-papazian]

Metrics were added during R&D phase on API Security. This PR removes them.
It prevents to send unneeded data to DD backend.

APPSEC-52415

https://github.com/DataDog/dd-analytics/pull/30330 is also put in place to ensure no additional charges for customers using non updated tracers.

This PR is backported to all versions containing api security.

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: christophe-papazian/remove_api_security_span_metrics
Commit report: 82b34cb
Test service: dd-trace-py

✅ 0 Failed, 338 Passed, 111199 Skipped, 15m 18.8s Total duration (1h 34m 59.17s time saved)

[pr-commenter]

Benchmarks

Benchmark execution time: 2024-04-09 12:55:25

Comparing candidate commit 3c99d08 in PR branch christophe-papazian/remove_api_security_span_metrics with baseline commit 131837d in branch main.

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

scenario:flasksimple-appsec-get

• 🟩 execution_time [-280.160µs; -229.772µs] or [-4.280%; -3.511%]

scenario:httppropagationinject-ids_only

• 🟥 max_rss_usage [+567.007KB; +617.965KB] or [+2.667%; +2.907%]

scenario:httppropagationinject-with_all

• 🟥 max_rss_usage [+663.743KB; +789.518KB] or [+3.144%; +3.740%]

scenario:httppropagationinject-with_tags

• 🟥 max_rss_usage [+784.735KB; +829.908KB] or [+3.724%; +3.938%]

scenario:httppropagationinject-with_tags_max_size

• 🟥 max_rss_usage [+722.721KB; +778.873KB] or [+3.424%; +3.690%]

[github-actions]

The backport to 2.5 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.5 2.5
# Navigate to the new working tree
cd .worktrees/backport-2.5
# Create a new branch
git switch --create backport-8906-to-2.5
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 616c5a93ad26647a6b9cb98f45e9bc4a35687d83
# Push it to GitHub
git push --set-upstream origin backport-8906-to-2.5
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.5

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

[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-8906-to-2.6
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 616c5a93ad26647a6b9cb98f45e9bc4a35687d83
# Push it to GitHub
git push --set-upstream origin backport-8906-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-8906-to-2.6.

[github-actions]

The backport to 2.7 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.7 2.7
# Navigate to the new working tree
cd .worktrees/backport-2.7
# Create a new branch
git switch --create backport-8906-to-2.7
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 616c5a93ad26647a6b9cb98f45e9bc4a35687d83
# Push it to GitHub
git push --set-upstream origin backport-8906-to-2.7
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.7

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

[christophe-papazian]

Backports to 2.6 and 2.5 were cut directly from backport to 2.7