Add experimental renderToStringAsync parameter for renderApp

[jahredhope]

Reasoning/Details in ChangeSet

• Added TanStack's react-query to a new fixture, to more genuinely recreate a suspended component.
  • Unfortunately, I only found out towards the end it embeds the the date in the dehydrated state, so I put in a hack to set the date to SEEK's 100th anniversary (If the fixture is still in then, please update it).
• With some dependency management there were some unrelated fixture snapshot updates. I think the ignore file changes were actually always in there.

Testing

• Render doesn't fail, even with a suspended component in new suspense fixture.
• When testing using the fixture locally the 'loading todos' console message only appears on the server, not on the client. Unless you unmount/mount the component after render, in which case it'll be called on the client.

[changeset-bot]

🦋 Changeset detected

Latest commit: a74d7da

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
sku	Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[askoufis]

Thoughts on naming this something like:

Suggested change

	renderToString: (element: ReactNode) => Promise<string>;
	EXPERIMENTAL_renderToString: (element: ReactNode) => Promise<string>;

[jahredhope]

After some debate I'm now recommending calling it renderToStringAsync, this is:

• Better Visibility: Easily searchable in code-bases
• Better Migration: It's quite clear to consumers they now need to await the result
• Maybe a bit uglier: But happy to trade off for the above benefits

Whilst the support for this is experimental, it's not unreasonable to be taken to production with care. I wouldn't want to set a precedence where teams send things called EXPERIMENTAL_ to production.