fix: Media blob cache and chunk loading error handling

[Just-Insane]

Summary

This PR adds robust error handling for two types of client errors:

1. Unhandled Promise Rejection in Media Blob Cache (Commit 77046ab)

Fixes unhandled promise rejections when multiple components fetch the same media URL that fails with 401 errors.

Root Cause: When a blob fetch request was in-flight and failed, subsequent callers awaiting the same promise would receive an unhandled rejection because the await was outside the try-catch block.

Changes:

• Wrap inflightRequests.get() await in try-catch block
• Improve error messages to include HTTP status codes
• Add Service Worker logging for session retrieval failures to diagnose authentication issues

Addresses: Sentry Issue #1 (401 errors on authenticated media endpoints)

2. Automatic Retry for Chunk Loading Failures (Commit bff8c3d)

Adds automatic page reload when dynamic import failures occur due to stale HTML after deployments.

Root Cause: After deployments, users with cached HTML try to load JS chunks that no longer exist, causing "Failed to fetch dynamically imported module" errors.

Changes:

• Global error handler catches chunk load errors (ChunkLoadError, "Failed to fetch")
• Auto-reload page on first 2 failures without user intervention
• On 3rd failure, let error bubble to Sentry error boundary
• Uses sessionStorage to track retry count across reloads
• Clears counter on successful page load

Addresses: Sentry Issue #2 (stale HTML breaking app after deployments)

Testing

• Error handling paths verified through code review
• sessionStorage retry logic tested locally
• Both fixes address real production errors from Sentry