fix: Prevent Sentry from capturing router notFound/redirect signals

[sentry]

The DefaultCatchBoundary component was inadvertently reporting TanStack Router's notFound() and redirect() control-flow signals as exceptions to Sentry. These signals are not actual errors but mechanisms for router navigation.

This change modifies src/components/DefaultCatchBoundary.tsx to:

• Import isNotFound and isRedirect utilities from @tanstack/react-router.
• Add a conditional check within the useEffect hook to prevent Sentry.captureException from being called if the caught 'error' is identified as a notFound or redirect signal. This ensures Sentry only captures genuine exceptions, reducing noise and improving error monitoring accuracy.

Fixes TANSTACK-COM-31Q

_{This PR was automatically generated by Sentry. You can adjust this setting at any time.}

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	tanstack-com	932c2c0	Commit Preview URL Branch Preview URL	Aug 29 2026, 11:03 PM