fix(next-auth): allow users to use the application offline (#115)

**Why:**
When a user is offline and runs an application, he will always be unauthorized. For my app, I temporarily changed the cache config and now suggesting the same changes.

**What changed:**
- Update the list of URLs excluded from caching by making it more specific: `/api/auth/` => `/api/auth/callback/`.
- Google Auth is tested in _Chrome 119 arm64 for macOS_, _Safari 17.0 for macOS_ ans _Safari for iOS 17.1.1_.
- Opening pages offline works fine, tested in the same browsers.
- Tested logging out when the user is online and the token is not valid.

Author: vlad-iakovlev

.changeset/honest-dots-grow.md

@@ -0,0 +1,5 @@
+---
+"@ducanh2912/next-pwa": patch
+---
+
+fix(next-auth): allow users to use the application offline

packages/next-pwa/src/cache.ts

@@ -141,7 +141,7 @@ const defaultCache: RuntimeCaching[] = [
       // Exclude /api/auth/callback/* to fix OAuth workflow in Safari without having an impact on other environments
       // The above route is the default for next-auth, you may need to change it if your OAuth workflow has a different callback route
       // Issue: https://github.com/shadowwalker/next-pwa/issues/131#issuecomment-821894809
-      if (!sameOrigin || pathname.startsWith("/api/auth/")) {
+      if (!sameOrigin || pathname.startsWith("/api/auth/callback")) {
         return false;
       }