DEBUG-3700 Do not initialize components from on crashtracking fork handler

[p-datadog]

What does this PR do?

Motivation:

Change log entry

Additional Notes:

How to test the change?

[github-actions]

👋 Hey @p-datadog, please fill "Change log entry" section in the pull request description.

If changes need to be present in CHANGELOG.md you can state it this way

**Change log entry**

Yes. A brief summary to be placed into the CHANGELOG.md

(possible answers Yes/Yep/Yeah)

Or you can opt out like that

**Change log entry**

None.

(possible answers No/Nope/None)

^{Visited at: 2025-05-01 20:54:22 UTC}

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 97.76%. Comparing base (65cb319) to head (dfb0d36).

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #4619   +/-   ##
=======================================
  Coverage   97.76%   97.76%           
=======================================
  Files        1412     1412           
  Lines       86236    86235    -1     
  Branches     4348     4348           
=======================================
  Hits        84307    84307           
+ Misses       1929     1928    -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[datadog-datadog-prod-us1]

Datadog Report

Branch report: crashtracking-component-tree
Commit report: dfb0d36
Test service: dd-trace-rb

✅ 0 Failed, 21033 Passed, 1372 Skipped, 3m 37.7s Total Time

[pr-commenter]

Benchmarks

Benchmark execution time: 2025-05-07 22:14:41

Comparing candidate commit dfb0d36 in PR branch crashtracking-component-tree with baseline commit 65cb319 in branch master.

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

scenario:profiling - Allocations ()

• 🟥 throughput [-337952.112op/s; -292603.103op/s] or [-10.258%; -8.881%]

[ivoanjo]

I'm curious what drove this change (I checked the JIRA ticket and didn't have any details about this).

In particular, the at_fork in the crashtracker gets applied once the crashtracker is initialized by the components, so I don't understand in what situation we'd go back to a case where the components are not initialized again after that?