useFetch - options for gracefully refetching

[jmroon]

Clear and concise description of the problem

When using useFetch, If you are writing to the url ref fairly quickly, there's no guarantee that the last url value in useFetch will be the one returned. You can test this fairly easily by quickly changing the url parameter on the useFetch page with refetch on:
https://vueuse.org/core/useFetch/

Since the requests can return out of order, you can run into issues where you get a 404 on a correct url or have the error become out of sync:

Suggested solution

Could this perhaps be addressed by allowing previous requests to be automatically aborted if the url value changes?

Alternative

No response

Additional context

No response

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

[Alfred-Skyblue]

resolved #2750