fix(persisted): Add dev warning for persisted-miss results for an already persisted-miss errored operation (repeated retries)

[kitten]

Closes #3441

Summary

When a persistedExchange() sees a persisted-miss error, it will retry the operation while disabling persisted serialization using the miss: true flag. However, we had no guard to check whether miss: true was already set.

This meant that if an API/exchange erroneously keeps replying with persisted-miss errors then persistedExchange() wouldn't stop retrying the operation.
When an ssrExchange() on the server-side caches this error, this is made worse, since ssrExchange's results are synchronous and this hence causes an infinite loop.

A development-time warning has been added that explicitly tells people that this is what's going on and how to resolve it.

Set of changes

• Add failing test for repeated persisted-miss errors
• Handle & Ignore repeated persisted-miss errors and log development warning

[changeset-bot]

🦋 Changeset detected

Latest commit: 3848395

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

This PR includes changesets to release 1 package

Name	Type
@urql/exchange-persisted	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