fix(profiling): placement new for all containers post fork

[KowalskiThomas]

Description

This PR fixes more, even rarer post-fork crashes detected through Crash Logs (< 10 per day).

The fix is to "hard reset" with a placement-new instead of clear or whatever the "usual" way to reset is. The reason (still) is that the Sampling Thread may be mid-sampling / mid heap operation when the fork happens, in which case the STL containers we use may be left in an inconsistent state in the child process where the previously-working thread doesn't exist anymore.

[cit-pr-commenter-54b7da]

Codeowners resolved as

releasenotes/notes/profiling-fix-post-fork-crashes-00cc0d66244567c2.yaml  @DataDog/apm-python

[datadog-official]

 

✨ Fix all issues with BitsAI

⚠️ Warnings

🚦 8 Pipeline jobs failed

DataDog/apm-reliability/dd-trace-py | build linux serverless: [amd64, cp315-cp315, v113741238-d2b8243-manylinux2014_x86_64, 1]     

DataDog/apm-reliability/dd-trace-py | build linux serverless: [amd64, cp315-cp315, v113741491-d2b8243-musllinux_1_2_x86_64, 1]     

DataDog/apm-reliability/dd-trace-py | build linux serverless: [arm64, cp315-cp315, v113741357-d2b8243-manylinux2014_aarch64, 1]     

View all 8 failed jobs.

ℹ️ Info

No other issues found (see more)

🧪 All tests passed
❄️ No new flaky tests detected

🔄 Datadog auto-retried 1 job - 1 passed on retry

Useful? React with 👍 / 👎

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 4776cfb | Docs | Datadog PR Page | Give us feedback!}

[github-actions]

This change is marked for backport to 4.10 and it does not conflict with that branch.
The command used to test backporting was

git fetch origin 4.10 && git checkout origin/4.10 && git checkout -b backport--to-4.10 && git cherry-pick -x --mainline 1 18acf341a05695c534ae3a4ae883ef578a451b7a

[github-actions]

This change is marked for backport to 4.8 and it does not conflict with that branch.
The command used to test backporting was

git fetch origin 4.8 && git checkout origin/4.8 && git checkout -b backport--to-4.8 && git cherry-pick -x --mainline 1 18acf341a05695c534ae3a4ae883ef578a451b7a

[github-actions]

This change is marked for backport to 4.11 and it does not conflict with that branch.
The command used to test backporting was

git fetch origin 4.11 && git checkout origin/4.11 && git checkout -b backport--to-4.11 && git cherry-pick -x --mainline 1 18acf341a05695c534ae3a4ae883ef578a451b7a

[github-actions]

This change is marked for backport to 4.9 and it does not conflict with that branch.
The command used to test backporting was

git fetch origin 4.9 && git checkout origin/4.9 && git checkout -b backport--to-4.9 && git cherry-pick -x --mainline 1 18acf341a05695c534ae3a4ae883ef578a451b7a

[KowalskiThomas]

@codex review

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 4776cfb81e

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[gyuheon0h]

Should we add identified by crashtracker if it was ID by crash logs