fix(iast): fix potential memory leak on IAST exception handling [backport-2.13]

[juanjux]

Description

Partial manual backport of the memleak fix in #10755.

Checklist

• PR author has checked that all the criteria below are met
• The PR description includes an overview of the change
• The PR description articulates the motivation for the change
• The change includes tests OR the PR description describes a testing
  strategy
• The PR description notes risks associated with the change, if any
• Newly-added code is easy to change
• The change follows the library release note
  guidelines
• The change includes or references documentation updates if necessary
• Backport labels are set (if
  applicable)

Reviewer Checklist

• Reviewer has checked that all the criteria below are met
• Title is accurate
• All changes are related to the pull request's stated goal
• Avoids breaking
  API
  changes
• Testing strategy adequately addresses listed risks
• Newly-added code is easy to change
• Release note makes sense to a user of the library
• If necessary, 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

Co-authored-by: Emmett Butler [email protected]## Checklist

• PR author has checked that all the criteria below are met
• The PR description includes an overview of the change
• The PR description articulates the motivation for the change
• The change includes tests OR the PR description describes a testing strategy
• The PR description notes risks associated with the change, if any
• Newly-added code is easy to change
• The change follows the library release note guidelines
• The change includes or references documentation updates if necessary
• Backport labels are set (if applicable)

Reviewer Checklist

• Reviewer has checked that all the criteria below are met
• Title is accurate
• All changes are related to the pull request's stated goal
• Avoids breaking API changes
• Testing strategy adequately addresses listed risks
• Newly-added code is easy to change
• Release note makes sense to a user of the library
• If necessary, 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

[github-actions]

CODEOWNERS have been resolved as:

releasenotes/notes/memleak-on-iast-error-handling-464f52f5fbeb5e24.yaml  @DataDog/apm-python
ddtrace/appsec/_iast/_taint_tracking/Utils/GenericUtils.cpp             @DataDog/asm-python

[datadog-dd-trace-py-rkomorn]

Datadog Report

Branch report: juanjux/backport-memleak-to-213
Commit report: d6e0240
Test service: dd-trace-py

✅ 0 Failed, 1946 Passed, 213 Skipped, 1m 52.28s Total duration (1m 20.59s time saved)

[pr-commenter]

Benchmarks

Benchmark execution time: 2024-09-25 07:25:59

Comparing candidate commit d6e0240 in PR branch juanjux/backport-memleak-to-213 with baseline commit 3942e52 in branch 2.13.

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