Backoff upon error during auto refresh

[pixtron]

Bug report

Describe the bug

Backoff during auto refresh upon network failure fails in 1.23.0-next.

To Reproduce

1. clone the repro
2. npm install
3. npm start
4. Signup with email and password (or login if you already have an account)
5. Disable all network interfaces
6. Wait 2 minutes until token expires and auto refresh is triggered

The refresh request fails due to the client being offline. The client does not backoff and retry with further requests.

Expected behavior

The client should backoff and retry to refresh the token.

Suggested fix

This regression seems to have been introduced in 1.23.0-next in lib/fetch.ts with #301.

1. Introduce a new Error AuthNetworkFailureError exends AuthError
2. Throw AuthNetworkFailureError instead of AuthUnknownError. Fetch only throws on a network error (unfortunately there seems to be no way to distinguish between network errors and CORS though).
3. Replace the check error?.message === NETWORK_FAILURE.ERROR_MESSAGE with error instanceof AuthNetworkFailureError
4. Remove constant NETWORK_FAILURE.ERROR_MESSAGE

System information

• OS: NA
• Browser: NA
• Version of supabase-js: NA
• Version of gotrue-js: 1.23.0-next.6
• Version of Node.js: NA

Additional context

The same mal function can probably be observed in _recoverAndRefresh.

[github-actions]

🎉 This issue has been resolved in version 1.23.0-next.17 🎉

The release is available on:

• GitHub release
• npm package (@next dist-tag)

Your semantic-release bot 📦🚀

[github-actions]

🎉 This issue has been resolved in version 2.0.0-rc.1 🎉

The release is available on:

• GitHub release
• npm package (@rc dist-tag)

Your semantic-release bot 📦🚀

[kangmingtay]

closing this since it's been resolved by the PRs above! thanks @pixtron once again :)