Handle SSE token expiration silently to avoid Sentry noise

[jnMetaCode]

Summary

• Fixes the SSE client error handler in useTriggerEventStreamCreation to detect token expiration errors (401/UNAUTHENTICATED) and handle them silently by triggering event stream reconnection
• Non-token-expiration errors continue to be reported to Sentry as before
• This prevents excessive Sentry error logs caused by normal idle session token expiry, which is a standard reconnection scenario

Fixes #18077

Test plan

• Verify that when a session goes idle and the token expires, no error is sent to Sentry
• Verify that the SSE client reconnects normally after token expiration
• Verify that genuine SSE errors (non-auth) are still captured in Sentry

[greptile-apps]

Your free trial has ended. If you'd like to continue receiving code reviews, you can add a payment method here.

[github-actions]

Welcome!

Hello there, congrats on your first PR! We're excited to have you contributing to this project.
By submitting your Pull Request, you acknowledge that you agree with the terms of our Contributor License Agreement.

Generated by 🚫 dangerJS against b7fb1e9

[cubic-dev-ai]

No issues found across 1 file

[sentry]

Bug: The new 401 error handler triggers an infinite SSE reconnection loop because it does not refresh the expired authentication token before attempting to reconnect.
_{Severity: HIGH}

Suggested Fix

Instead of silently triggering a reconnection on a 401 error, the handler should initiate a token refresh mechanism or trigger a user-facing re-authentication flow. The reconnection should only proceed after the token has been successfully refreshed. Persistent authentication failures should be logged to ensure visibility.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location:
packages/twenty-front/src/modules/sse-db-event/hooks/useTriggerEventStreamCreation.ts#L127-L130

Potential issue: When the authentication token expires, the SSE client receives a 401
error. The new error handler in `useTriggerEventStreamCreation.ts` catches this and sets
`shouldDestroyEventStreamState` to `true`, initiating a destroy-and-recreate cycle for
the event stream. However, the client-side application lacks a mechanism to
automatically refresh the expired token. Consequently, the new SSE stream is created
with the same invalid token, leading to another 401 error. This results in a silent,
infinite reconnection loop, consuming client and server resources without notifying the
user of the session expiration or logging the error.

_{Did we get this right? 👍 / 👎 to inform future reviews.}

[charlesBochet]

@jnMetaCode Please stop opening AI generated PR on this repository. You are not helping us and harming the community. This will be the only warning before ban: one more and that's it