fix(tracer): fix multiprocessing queue on aws lambda

[christophe-papazian]

#6929 introduced a bug as multiprocessing.Queue is not supported on AWS lambda platform.
This fix prevents the use of the Queue on aws lambda, as this is used for a RC only feature, and lambda does not use RC.

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-20 18:09:03

Comparing candidate commit 8555f1e in PR branch christophe-papazian/fix-multiprocessing-queue-for-lambda with baseline commit 1c9765f in branch 2.x.

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

scenario:otelspan-start-finish-telemetry

• 🟩 max_rss_usage [-834.599KB; -655.935KB] or [-2.750%; -2.161%]

scenario:tracer-large

• 🟩 max_rss_usage [-1.242MB; -1.067MB] or [-4.140%; -3.555%]

scenario:tracer-medium

• 🟩 max_rss_usage [-861.266KB; -672.686KB] or [-2.961%; -2.313%]

scenario:tracer-small

• 🟩 max_rss_usage [-924.571KB; -738.405KB] or [-3.179%; -2.539%]

[astuyve]

Approved for Serverless, this seems to fix #7251

[github-actions]

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

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

[github-actions]

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

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