fix(prof) follow PHP globals model

[realFlowControl]

Description

Since supporting ZTS versions of PHP, we started storing our profiler state in TLS (thread local storage). The assumption was that in PHP ZTS this would store the state per thread and helped us support ZTS PHP, while in NTS it would still store state in a TLS variable, but as there is only one thread, what gives!
Now it turns out there is at least one extension out there which does the following:

• PHP userland code calls into an \extension\namespace\do_somthing() function
• the C-implementation of that PHP function spawns a thread (even in NTS PHP)
• this other thread might execute a closure that was given to an init function of the extension earlier
• this closure might now as well allocate memory on the ZendMM
• As our profiler has installed it's own custom ZendMM, we get called to track the allocation
• we need to forward to the original ZendMM for the actuall allocation
• to find that, we look it up in the TLS allocation state variable
• which is not initialised (as that thread is not a PHP thread) so we crash 💥

Even though what that extension is doing is a race condition and violates thread safety, we should still not crash. Basically what the allocation profiler did was to make a race condition that might crash super seldom into a 100% guaranteed crash 😜

PROF-11471

Reviewer checklist

• Test coverage seems ok.
• Appropriate labels assigned.

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 79.28%. Comparing base (aeeec62) to head (2bdc1c9).
Report is 3 commits behind head on master.

Additional details and impacted files

@@             Coverage Diff              @@
##             master    #3175      +/-   ##
============================================
+ Coverage     76.38%   79.28%   +2.89%     
  Complexity     2948     2948              
============================================
  Files           145      118      -27     
  Lines         16076    11633    -4443     
  Branches       1107        0    -1107     
============================================
- Hits          12280     9223    -3057     
+ Misses         3221     2410     -811     
+ Partials        575        0     -575     

Flag	Coverage Δ
appsec-extension	?
tracer-php	79.28% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

see 27 files with indirect coverage changes

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update aeeec62...2bdc1c9. Read the comment docs.

🚀 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.

[pr-commenter]

Benchmarks [ profiler ]

Benchmark execution time: 2025-04-30 15:30:46

Comparing candidate commit 2bdc1c9 in PR branch florian/zts-global-state with baseline commit aeeec62 in branch master.

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

scenario:walk_stack/50

• 🟥 wall_time [+738.839ns; +752.419ns] or [+4.866%; +4.955%]

scenario:walk_stack/99

• 🟥 wall_time [+740.223ns; +748.205ns] or [+4.877%; +4.929%]

[morrisonlevi]

I think this would still give a panic at the place we want, while not having string duplication. Linters (or maybe the compiler?) don't like panic having a constant as a format string, likes string literals.

diff --git a/profiling/src/allocation/mod.rs b/profiling/src/allocation/mod.rs
index 58437ebb9..e00158324 100644
--- a/profiling/src/allocation/mod.rs
+++ b/profiling/src/allocation/mod.rs
@@ -78,36 +78,41 @@ struct ZendMMState {
     shutdown: unsafe fn(bool, bool),
 }
 
-unsafe fn alloc_prof_panic_alloc(_len: size_t) -> *mut c_void {
+#[track_caller]
+fn init_panic() -> ! {
     panic!("Allocation profiler was not initialised properly. Please fill an issue stating the PHP version and the backtrace from this panic.");
 }
 
+unsafe fn alloc_prof_panic_alloc(_len: size_t) -> *mut c_void {
+    init_panic();
+}
+
 unsafe fn alloc_prof_panic_realloc(_prev_ptr: *mut c_void, _len: size_t) -> *mut c_void {
-    panic!("Allocation profiler was not initialised properly. Please fill an issue stating the PHP version and the backtrace from this panic.");
+    init_panic();
 }
 
 unsafe fn alloc_prof_panic_free(_ptr: *mut c_void) {
-    panic!("Allocation profiler was not initialised properly. Please fill an issue stating the PHP version and the backtrace from this panic.");
+    init_panic();
 }
 
 #[cfg(php_zend_mm_set_custom_handlers_ex)]
 unsafe fn alloc_prof_panic_gc() -> size_t {
-    panic!("Allocation profiler was not initialised properly. Please fill an issue stating the PHP version and the backtrace from this panic.");
+    init_panic();
 }
 
 #[cfg(php_zend_mm_set_custom_handlers_ex)]
 unsafe fn alloc_prof_panic_shutdown(_full: bool, _silent: bool) {
-    panic!("Allocation profiler was not initialised properly. Please fill an issue stating the PHP version and the backtrace from this panic.");
+    init_panic();
 }
 
 #[cfg(not(php_zend_mm_set_custom_handlers_ex))]
 fn prepare_zend_heap_panic(_heap: *mut zend::_zend_mm_heap) -> c_int {
-    panic!("Allocation profiler was not initialised properly. Please fill an issue stating the PHP version and the backtrace from this panic.");
+    init_panic();
 }
 
 #[cfg(not(php_zend_mm_set_custom_handlers_ex))]
 fn restore_zend_heap_panic(_heap: *mut zend::_zend_mm_heap, _custom_heap: c_int) {
-    panic!("Allocation profiler was not initialised properly. Please fill an issue stating the PHP version and the backtrace from this panic.");
+    init_panic();
 }
 
 impl ZendMMState {

[realFlowControl]

I've committed your suggestion