fix: Error retry should be handled by global revalidator instead of local revalidation function

[promer94]

close #2412 which was introduced in #2338

Problem

function Demo() {
   useSWR('/key', () => { throw new Error('error') })
   useSWR('/key', () => { throw new Error('error') })
}

Previously, if we have two swr hook, There will be two retry task pushed into queue. If first hook unmount, the error retry won't stop because of another task.

But after #2338, only the first mouted swr hook will schedule an error retry task using it own revalidate function.
If the first hook unmount, the revalidate function will become inactive because of

swr/core/use-swr.ts

Lines 263 to 270 in f7004ac

	if (
	!key ||
	!currentFetcher ||
	unmountedRef.current ||
	getConfig().isPaused()
	) {
	return false
	}

Solution

Instead of using local revalidate function for error retry, swr should always use the global event revalidator since it would be always active.

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit 61f7564:

Sandbox	Source
SWR-Basic	Configuration
SWR-States	Configuration
SWR-Infinite	Configuration
SWR-SSR	Configuration
isValidating-infinite-render (forked)	Issue #2412