Add withRetry utility and retry user upsert on transient failures

[jbojcic1]

Summary

• Add reusable withRetry utility (app/lib/with-retry.ts) with exponential backoff (500ms, 1s, 2s, ... capped at 30s), configurable retry count or predicate, custom retry delay function, and abort signal support
• Wrap user upsert in _protected.tsx middleware with withRetry to handle transient network failures (fixes AGICASH-7D)
• Replace fetchQuery with withRetry for mint quote check in cashu-receive-quote-hooks.ts
• Unexport userQueryOptions in user-hooks.tsx

Test plan

• Verify app loads normally (upsert succeeds on first try)
• Verify retry behavior by simulating network failure (e.g. throttle network in DevTools)
• Verify ZodError is not retried

Resolves https://make-prisms.sentry.io/issues/7310936806/?alert_rule_id=16176971&alert_type=issue&environment=production&notification_uuid=1f60e2dd-cfdf-49e3-867a-8b566da31fca&project=4509707316690944&referrer=discord

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
agicash	Ready	Preview, Comment	Mar 5, 2026 10:04pm

[supabase]

This pull request has been ignored for the connected project hrebgkfhjpkbxpztqqke because there are no changes detected in supabase directory. You can change this behaviour in Project Integrations Settings ↗︎.

---

Preview Branches by Supabase.
Learn more about Supabase Branching ↗︎.

[jbojcic1]

I added this so we can use it in places where we just need retires without the cache logic. We could have done this with react query fetchQuery (how it was before this change in cashu-receive-quote-hooks file where we had queryKey: ['check-mint-quote', receiveQuote.quoteId],) but if we do those we have these temp cache entries (we have to have some query key, gcTime and staleTime 0) which is a bit awkward