fix: Use no-cache for fetching registry (#3760)

To prevent users from having stale registry data, we fetch using
`no-cache` which always should recheck the registry for new updates
instead of relying on the browser cache. If the content has not changed
the browser will re-use the existing data and we keep falling back to
the previous version in state.

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> Ensure registry fetches bypass HTTP cache by calling fetch with {
cache: 'no-cache' } in safeFetch.
> 
> <sup>Written by [Cursor
Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit
2afb2a3. This will update automatically
on new commits. Configure
[here](https://cursor.com/dashboard?tab=bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

Author: FrederikBolding

packages/snaps-controllers/src/snaps/registry/json.ts

@@ -423,7 +423,7 @@ export class JsonSnapsRegistry extends BaseController<
    * @private
    */
   async #safeFetch(url: string) {
-    const response = await this.#fetchFunction(url);
+    const response = await this.#fetchFunction(url, { cache: 'no-cache' });
     if (!response.ok) {
       throw new Error(`Failed to fetch ${url}.`);
     }