Handle Safari SecurityErrors

According to ProtonMail, Safari can disable session storage under certain circumstances, so this needs to be detected and handled (session keys will not persist across hard reloads in those cases).

Look at the session storage usage in the library, likely in the browser-specific modules. Add a try-catch around sessionStorage access to detect SecurityError. When caught, fallback to an in-memory store or handle gracefully. Check existing tests for session storage mocking to add a test for this error case.

Vom Indexierungsmodell aus dem Issue-Text verfasst.