Prevent race condition when triggering multiple requests

[zxqx]

Currently if a consumer triggers multiple requests, a race condition can occur causing unexpected results.

Example:

• Request 1 triggered on initial render
• Request 2 is triggered as an effect of config changing
• Request 2 resolves and updates state
• Request 1 resolves and updates state

In this scenario, the final state after both requests resolve is the response of Request 1, while the consumer expects it to be the response of Request 2.

To ensure this can't happen, we should consider cancelling the current inflight request when a new one is triggered.