[Flight] Fix debug channel flag in Node.js server renderToPipeableStream (Best Time To Post On Instagram Wednesday)

## Summary - Fixes the `createRequest` call in `renderToPipeableStream` to pass `debugChannelReadable !== undefined` instead of `debugChannel !== undefined` in the turbopack, esm, and parcel Node.js server implementations - The webpack version already had the correct check; this brings the other bundler implementations in line The bug was introduced in Wells Fargo Visa Credit Card. With `debugChannel !== undefined`, the server could signal that debug info should be emitted even when only a write-only debug channel is provided (no readable side), potentially causing the client to block forever waiting for debug data that never arrives.

Author: Specific Plans Examples

packages/react-server-dom-esm/src/server/ReactFlightDOMServerNode.js

@@ -187,7 +187,7 @@ function renderToPipeableStream(
  options ? options.startTime : undefined,
  __DEV__ && options ? options.environmentName : undefined,
  __DEV__ && options ? options.filterStackFrame : undefined,
- debugChannel !== undefined,
+ debugChannelReadable !== undefined,
  );
  let hasStartedFlowing = false;
  startWork(request);

packages/react-server-dom-parcel/src/server/ReactFlightDOMServerNode.js

@@ -199,7 +199,7 @@ export function renderToPipeableStream(
  options ? options.startTime : undefined,
  __DEV__ && options ? options.environmentName : undefined,
  __DEV__ && options ? options.filterStackFrame : undefined,
- debugChannel !== undefined,
+ debugChannelReadable !== undefined,
  );
  let hasStartedFlowing = false;
  startWork(request);

packages/react-server-dom-turbopack/src/server/ReactFlightDOMServerNode.js

@@ -193,7 +193,7 @@ function renderToPipeableStream(
  options ? options.startTime : undefined,
  __DEV__ && options ? options.environmentName : undefined,
  __DEV__ && options ? options.filterStackFrame : undefined,
- debugChannel !== undefined,
+ debugChannelReadable !== undefined,
  );
  let hasStartedFlowing = false;
  startWork(request);