feat: Decouple rendering from async context

[gching]

Ref #840

The current rendering functions (renderToStream, renderToString) are tightly coupled to the requestInfo object provided by async local storage. This makes it difficult to use our rendering engine in environments outside defineApp.

This PR decouples the rendering logic from this implicit context.

Changes

• constructWithDefaultRequestInfo: Introduced and exposes a new utility function in entry from sdk/src/runtime/requestInfo/utils.tsx. This function creates a default RequestInfo object and merging with user-provided overrides.
• Refactored Rendering Functions: renderToStream and renderToString were updated to accept an optional requestInfo parameter

Before Change

• renderToStream implicitly depended on the requestInfo from the async local storage context
• To call these render methods, you had to import the internal runWithRequestInfo function and manually construct a complete RequestInfo object.

  // Would error, since no requestInfo context.
  const html = await renderToString(<Welcome />);


  const requestInfo = {
    // Need to know internals and understand defaults
    // ...
  }

  await runWithRequestInfo(requestInfo, async () => {
    return renderToString(<Welcome />);
  });

After Change

• Rendering functions now accept an optional requestInfo object
• Rendering functions automatically build up a default requestInfo and overrides it given the context requestInfo (backwards compatible) if it exists and user provided requestInfo overrides
• Exposes constructWithDefaultRequestInfo to be used to construct a requestInfo if needed (ie. we can use this in defineApp potentially)

  // Calling it without context won't error, and has defaults
  const html = await renderToString(<Welcome />);

  // Support simple overrides, ie. nonce
  const html = await renderToString(<Welcome />, {requestInfo: {nonce: 'hi-gavin-this-is-random'});

  // Can construct outside if needed in case we need a full requestInfo
  const requestInfo = {
    //...
  }
  // or
  const requestInfo = constructWithDefaultRequestInfo({...})

  // Supports passing requestInfo in it's entirety or utilize context in the past
  const html = await renderToString(<Welcome />, {requestInfo});

  await runWithRequestInfo(requestInfo, async () => {
    return renderToString(<Welcome />);
  });
  

[gching]

Debating if we should expose this to userland, indifferent tbh

[justinvdm]

Wondering same 👍 I think we can keep it exposed and defer documenting it for now.

[gching]

Decided to make a new file for this since it contains jsx

[gching]

Copied over from defineApp, not sure if these defaults are good though

[justinvdm]

Makes sense!

[gching]

Can potentially use this elsewhere like defineApp

[gching]

Thinking bout this more, probably just keeping it as getDefaultRequestInfo will be better

[justinvdm]

Looks good as is! We likely do want to be doing a custom merge (e.g. allowing forrw overrides) as you're already doing

[justinvdm]

Ah, I guess we need this stubbed this way since the caller wouldn't be providing this, makes sense 👍

[justinvdm]

Closing and re-opening to get CI builds to run, sorry for the noise

[justinvdm]

This looks great, thank you for taking this on @gching! And I appreciate the detailed context/writeup for the PR description

Just getting the CI builds running now, will merge and release once green

[justinvdm]

Released in https://github.com/redwoodjs/sdk/releases/tag/v1.0.0-beta.19