docs: fix release note for #7612 [backport 2.3] (#7710)

Backport d5ae475 from #7706 to 2.3.

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

## Checklist

- [x] Change(s) are motivated and described in the PR description.
- [x] Testing strategy is described if automated tests are not included
in the PR.
- [x] Risk is outlined (performance impact, potential for breakage,
maintainability, etc).
- [x] Change is maintainable (easy to change, telemetry, documentation).
- [x] [Library release note
guidelines](https://ddtrace.readthedocs.io/en/stable/releasenotes.html)
are followed. If no release note is required, add label
`changelog/no-changelog`.
- [x] Documentation is included (in-code, generated user docs, [public
corp docs](https://github.com/DataDog/documentation/)).
- [x] Backport labels are set (if
[applicable](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting))

## Reviewer Checklist

- [x] Title is accurate.
- [x] No unnecessary changes are introduced.
- [x] Description motivates each change.
- [x] Avoids breaking
[API](https://ddtrace.readthedocs.io/en/stable/versioning.html#interfaces)
changes unless absolutely necessary.
- [x] Testing strategy adequately addresses listed risk(s).
- [x] Change is maintainable (easy to change, telemetry, documentation).
- [x] Release note makes sense to a user of the library.
- [x] Reviewer has explicitly acknowledged and discussed the performance
implications of this PR as reported in the benchmarks PR comment.
- [x] Backport labels are set in a manner that is consistent with the
[release branch maintenance
policy](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting)
- [x] 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`.
- [x] This PR doesn't touch any of that.

Co-authored-by: Tahir H. Butt <[email protected]>

Author: github-actions[bot]

scripts/releasenotes/notes/do-not-use-multiprocessing-queue-in-aws-lambda-99fd75820125906f.yaml renamed to releasenotes/notes/do-not-use-multiprocessing-queue-in-aws-lambda-99fd75820125906f.yaml

@@ -29,8 +29,8 @@ else
 fi
 echo "Base ref: ${BASE_REF}"
 
-# Check if they added a new file to releasenotes/notes
-if git diff --name-only --diff-filter=A "${BASE_REF}" | grep "^releasenotes/notes";
+# Check if they added a new file or renamed a file in releasenotes/notes
+if git diff --name-only --diff-filter=AR "${BASE_REF}" | grep "^releasenotes/notes";
 then
     echo "New release note found, success"
     exit 0