fix: remove sw cache storage entries when using self destroying option

[userquin]

This PR also includes:

• check if the client is a WindowClient before calling navigate, it can be Push/Sync worker (missing navigate method)
• bump to pnpm 8.11.0

closes #560

[netlify]

✅ Deploy Preview for vite-plugin-pwa-legacy ready!

Name	Link
🔨 Latest commit	7152c61
🔍 Latest deploy log	https://app.netlify.com/sites/vite-plugin-pwa-legacy/deploys/65622e55ca4ad000088d2006
😎 Deploy Preview	https://deploy-preview-609--vite-plugin-pwa-legacy.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[Doctor-wu]

@userquin I noticed that you deleted all the keys in cache-storage, maybe deleting keys generated by this plugin will be better?

[userquin]

@Doctor-wu this plugin doesn't add any entry to the cache storage, the sw cache storage is per location (sw origin)

[Doctor-wu]

@userquin users can use sw outside this plugin, and they can add other caches even if that is not recommended, but we can't prevent users from doing that. Thus maybe we can delete the cache literally declared in the workbox's runtimeCaching, so that we won't delete the cache outside this plugin

[userquin]

@Doctor-wu we cannot detect user entries, you can use a custom one https://vite-pwa-org.netlify.app/guide/unregister-service-worker.html#custom-selfdestroying-service-worker

EDIT: if missing await until new version installed (prompt should be shown a few seconds later)

[Doctor-wu]

@userquin Got you~, maybe we can inform users in docs that we will delete all the cache when they use self-destroying

[userquin]

@userquin Got you~, maybe we can inform users in docs that we will delete all the cache when they use self-destroying

Check the INFO block:

[Doctor-wu]

Sry, I only watched the danger block😂, and now that will be pretty good~