(next) - fix issue with next where staleWhileRevalidate would loop

[JoviDeCroock]

Summary

Relates to #1888

When next resolves getStaticProps we rely on the props.urqlState to be hydrated during the renderToString this ensures that we actually use the data from this call on the server. The issue presents itself when we are in a renderToString pass and the exchange opts to mark the result as stale and perform a reexecute.

Set of changes

• avoid data being reexecuted due to staleWhileRevalidate on the server

[changeset-bot]

🦋 Changeset detected

Latest commit: 76dc5f0

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

This PR includes changesets to release 1 package

Name	Type
next-urql	Patch

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

[SteveMelons]

It seems like this issue was not resolved. I updated to v3.2.1. When setting staleWhileRevalidate to true, the page freezes on load and becomes unresponsive while using up 100% CPU.

[field123]

Have the same issue as @SteveMelons unresponsive page after a few seconds with staleWhileRevalidate set to true. v3.2.1

[JoviDeCroock]

@SteveMelons @field123 there was an oversight here #1944 will be fixing this, thank you for the ping 🙌