docs: fix release note for #7612 [backport 2.2]

[github-actions]

Backport d5ae475 from #7706 to 2.2.

The release note in #7612 was not in the correct directory.

Checklist

• Change(s) are motivated and described in the PR description.
• Testing strategy is described if automated tests are not included in the PR.
• Risk is outlined (performance impact, potential for breakage, maintainability, etc).
• Change is maintainable (easy to change, telemetry, documentation).
• Library release note guidelines are followed. If no release note is required, add label changelog/no-changelog.
• Documentation is included (in-code, generated user docs, public corp docs).
• Backport labels are set (if applicable)

Reviewer Checklist

• Title is accurate.
• No unnecessary changes are introduced.
• Description motivates each change.
• Avoids breaking API changes unless absolutely necessary.
• Testing strategy adequately addresses listed risk(s).
• Change is maintainable (easy to change, telemetry, documentation).
• Release note makes sense to a user of the library.
• Reviewer has explicitly 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
• If this PR touches code that signs or publishes builds or packages, or handles credentials of any kind, I've requested a review from @DataDog/security-design-and-guidance.
• This PR doesn't touch any of that.

[pr-commenter]

Benchmarks

Benchmark execution time: 2023-11-21 16:54:57

Comparing candidate commit 2ffa5a5 in PR branch backport-7706-to-2.2 with baseline commit 4fd3010 in branch 2.2.

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

scenario:flasksimple-appsec-telemetry

• 🟥 max_rss_usage [+1.079MB; +1.267MB] or [+3.095%; +3.633%]

scenario:flasksimple-baseline

• 🟥 execution_time [+96.313µs; +120.919µs] or [+2.081%; +2.612%]