(fix) - Fix timing for out-of-band client.reexecuteOperation calls

[kitten]

Resolve #721

Summary

When an operation becomes asynchronous, by matter of an exchange
delaying it, while it also calls client.reexecuteOpoeration, we
were calling client.reexecuteOperation out-of-band, which causes
the reexecuted operation to be dispatched immediately.
We can't detect the intent of the exchange, and don't know that it
may afterwards immediately send a result synchronously after the delay,
but we do know that once an operation becomes asynchronous, the timing
of client.reexecuteOperation is not sensitive anymore. So instead we
now choose to defer it by a tick.

Set of changes

• Add a defer to @urql/core
• Defer flushing the queue actively in reexecuteOperation when no other operation is in-band and actively being worked on

[changeset-bot]

🦋 Changeset is good to go

Latest commit: 0697baf

We got this.

This PR includes changesets to release 1 package

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