Fix: Prevent cascading 401 errors by forcing logout on token expiration

[seer-by-sentry]

This PR addresses an issue where the application would get stuck in a loop of failed API calls (cascading 401 errors) if the stored OAuth token became invalid, expired, or was revoked.

Changes:

1. API Error Handling: Introduced logic in SentryApiMiddleware to detect HTTP 401 responses (ApiError.isAuthenticationError).
2. Forced Logout: When a 401 is detected, an AuthenticationRequiredAction is dispatched.
3. Credential Cleanup: The SecureStorageMiddleware handles this action by clearing the stored authToken and dispatching a LogoutAction.

This ensures that users are gracefully logged out and prompted to re-authenticate immediately upon token invalidation, preventing continuous failed requests.