feat: Add docs about request isolation in Node SDK (#11378)

---------

Co-authored-by: Lukas Stracke <lukas.stracke@sentry.io>
Co-authored-by: Liza Mock <liza.mock@sentry.io>

docs/platforms/javascript/common/enriching-events/request-isolation/index.mdx

@@ -0,0 +1,36 @@
+---
+title: Request Isolation
+description: "Learn more about how request isolation (or process isolation) works in the Sentry SDK."
+supported:
+  - javascript.nextjs
+  - javascript.node
+  - javascript.connect
+  - javascript.express
+  - javascript.fastify
+  - javascript.hapi
+  - javascript.koa
+  - javascript.nestjs
+  - javascript.nuxt
+  - javascript.solidstart
+  - javascript.sveltekit
+  - javascript.astro
+  - javascript.remix
+notSupported:
+  - javascript
+---
+
+In server-side environments, the <PlatformLink to='/enriching-events/scopes'>isolation scope</PlatformLink> automatically forks around request boundaries. This is done automatically by the SDK. As a result, each request has its own isolation scope, and data set on the isolation scope only applies to events captured during that request. 
+
+However, there are also other times when you may want to have isolation, for example, in background jobs or when you want to isolate a specific part of your code. In these cases, you can use `Sentry.withIsolationScope()` to create a new isolation scope that's valid inside of the callback you pass to it. Learn more about using [withIsolationScope](../scopes/#using-withisolationscope).
+
+The following example shows how you can use `withIsolationScope` to attach data to a specific job run:
+
+```javascript
+async function job(jobId) {
+  return Sentry.withIsolationScope(async () => {
+    // Only valid for events in this callback
+    Sentry.setTag("jobId", jobId);
+    await doSomething();
+  });
+}
+```

docs/platforms/javascript/common/enriching-events/scopes/index.mdx

@@ -143,3 +143,13 @@ In the following example we use <PlatformIdentifier name="with-scope" /> to atta
 The scope inside the `withScope()` callback is only valid inside of the callback. Once the callback ends, the scope will be removed and no longer applied. The inner scope is only applied to events that are captured inside of the callback. `withScope()` will clone (or fork) the current scope, so that the current scope is not modified. This allows you to
 more easily isolate pieces of context information to specific locations in your code or
 even call <PlatformIdentifier name="clear" /> to briefly remove all context information.
+
+<PlatformCategorySection supported={['server']}>
+## Using `withIsolationScope`
+
+`withIsolationScope` works fundamentally the same as `withScope`, but it will fork the isolation scope instead of the current scope. Generally, the isolation scope is meant to be forked less frequently than the current scope, and in most cases the SDK will handle this automatically for you.
+
+But in cases where you e.g. want to isolate a non-request process (e.g. a background job), you can use `withIsolationScope` to create a new isolation scope that is only active for the duration of the callback:
+
+<PlatformContent includePath="enriching-events/scopes/with-isolation-scope" />
+</PlatformCategorySection>

platform-includes/enriching-events/scopes/with-isolation-scope/javascript.mdx

@@ -0,0 +1,13 @@
+```javascript
+Sentry.withIsolationScope(function () {
+  // This user & tag is set inside of this callback
+  Sentry.setUser({ id: "123" });
+  Sentry.setTag("my-tag", "my value");
+
+  // will be tagged with my-tag="my value" & user
+  Sentry.captureException(new Error("my error"));
+});
+
+// will not be tagged with my-tag & user
+Sentry.captureException(new Error("my other error"));
+```