Fix token expiration error loop (#6731)

[eliasylonen]

Fixes issue #6731

Problem: After access token token expires, scrolling down the RecordTable component will put it to an infinite loop of trying to fetch records and printing errors on every iteration.

Solution: Disable fetching until component remount if a FORBIDDEN error is encountered.

[greptile-apps]

PR Summary

This PR implements error handling for token expiration in the RecordTable component to prevent infinite fetch loops when scrolling.

• Added tableEncounteredUnrecoverableErrorComponentState to track FORBIDDEN errors in /packages/twenty-front/src/modules/object-record/record-table/states/tableEncounteredUnrecoverableErrorComponentState.ts
• Modified fetchMoreRecords in useFetchMoreRecordsWithPagination.ts to return error information for FORBIDDEN detection
• Added error state handling in RecordTableNoRecordGroupBodyEffect.tsx to stop fetching when FORBIDDEN errors occur
• Implemented error detection logic to prevent further fetch attempts until component remount

_{💡 (1/5) You can manually trigger the bot by mentioning @greptileai in a comment!}

_{3 file(s) reviewed, 1 comment(s)
Edit PR Review Bot Settings | Greptile}

[FelixMalfait]

Perfect! thank you!

[charlesBochet]

Agree with the strat, I think we could do it for all errors (not only FORBIDDEN)
Thanks for fixing this one!

[FelixMalfait]

@charlesBochet I'm not sure that's a good idea. In the case of forbidden you know the user will get kicked out and things will be reset. In other cases it seems to be a trickier problem (when should we allow fetch more again?), might be best to solve it when we know for sure it causes an issue / have real-life examples

[charlesBochet]

ok, LGTM!