fix: Reflect most recent node version support for node profiling

Author: AbhiPrasad

platform-includes/profiling/node-profiling/javascript.mdx

@@ -115,11 +115,11 @@ Under the hood, the Sentry profiler uses V8's [CpuProfiler](https://v8docs.nodes
 
 ## Precompiled Binaries
 
-Starting from version `0.1.0`, the `@sentry/profiling-node` package precompiles binaries for a number of common architectures. This minimizes the tooling required to run the package and avoids compiling the package from source in most cases, which speeds up installation. Currently, we ship prebuilt binaries for the following architectures and Node versions:
+The `@sentry/profiling-node` package precompiles binaries for a number of common architectures. This minimizes the tooling required to run the package and avoids compiling the package from source in most cases, which speeds up installation. Currently, we ship prebuilt binaries for the following architectures and Node versions:
 
-- macOS x64: Node v16, v18, v20, v22
-- Linux ARM64 (musl): Node v16, v18, v20, v22
-- Linux x64 (glibc): Node v16, v18, v20, v22
-- Windows x64: Node v16, v18, v20, v22
+- macOS x64: Node v18, v20, v22, v24
+- Linux ARM64 (musl): Node v18, v20, v22, v24
+- Linux x64 (glibc): Node v18, v20, v22, v24
+- Windows x64: Node v18, v20, v22, v24
 
 The set of common architectures should cover a wide variety of use cases, but if you have feedback or experience different behavior, please open an issue in the [Sentry JavaScript SDK](https://github.com/getsentry/sentry-javascript) repository.