fix(profiling-node): Bump @sentry/node-cpu-profiler to 2.4.4 (#24229)

Bumps `@sentry/node-cpu-profiler` to 2.4.4 so profile chunks get
`debug_meta` images when only native debug IDs are registered.

The profiler only collected script resources when the legacy
`_sentryDebugIds` global was set. Bundlers with native debug ID support,
such as Turbopack, only write `_debugIds`, so profile chunks shipped
with an empty `debug_meta` and were never symbolicated. 2.4.4 accepts
either global (getsentry/sentry-javascript-profiling-node-binaries#40).

Fixes #24202

Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>

Author: chargome

packages/profiling-node/package.json

@@ -50,7 +50,7 @@
     "test:watch": "vitest --watch"
   },
   "dependencies": {
-    "@sentry/node-cpu-profiler": "^2.4.3",
+    "@sentry/node-cpu-profiler": "^2.4.4",
     "@sentry/core": "10.67.0",
     "@sentry/node": "10.67.0"
   },

yarn.lock

@@ -7900,10 +7900,10 @@
   resolved "https://sfw.security.sentry.io/npm/@sentry/conventions/-/conventions-0.20.0.tgz#f73f6f46934d754dacef447755b5adf1bf7f3245"
   integrity sha512-nAL3tL+xgom6Dbuxq0NCEZZfBNIrUspjDJRcMMRl3WLiBCSeZzNCa7an48IpnrZoVMpAi2NQ2v9rFU+EQziKuQ==
 
-"@sentry/node-cpu-profiler@^2.4.3":
-  version "2.4.3"
-  resolved "https://registry.yarnpkg.com/@sentry/node-cpu-profiler/-/node-cpu-profiler-2.4.3.tgz#1119aa07fb34672435fea3e386ade7dfe73fdf34"
-  integrity sha512-18g/yJKRUk4PNcnZYEPyT2nS+9UoFcTRrIrct1DbpfI7k//RtQ+8araZrR0WH5MT8xoiLCm67GEX/RcxDsI0iQ==
+"@sentry/node-cpu-profiler@^2.4.4":
+  version "2.4.4"
+  resolved "https://registry.yarnpkg.com/@sentry/node-cpu-profiler/-/node-cpu-profiler-2.4.4.tgz#b275d249bd6e0c98c1e4f2ebc87acf702e6ae04d"
+  integrity sha512-FaYbFWxEyTTVqXLJccokJCkwx2cTuvTiRaM9kA+O4HbZVT49xYXqSV9cNLI5UqJhgdHiZDhelBd5LB4wj7IIRA==
   dependencies:
     detect-libc "^2.0.3"
     node-abi "^3.73.0"