fix(auth): handle error properly in loadCurrentUser

[AMoreaux]

Updated the loadCurrentUser function to throw specific errors when an API error occurs. This improves clarity and error handling, replacing the generic "No current user result" exception.

Fix #9536

[greptile-apps]

PR Summary

Improved error handling in the authentication flow by adding specific API error messages in the loadCurrentUser function, replacing the generic "No current user result" error.

• Modified error handling in packages/twenty-front/src/modules/auth/hooks/useAuth.ts to check for API errors before accessing currentUser data
• Added error message propagation from API response for better debugging and user feedback
• Updated error handling in verify flow to properly handle authentication failures

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

[github-actions]

	Fails
🚫	node failed.

Log

�[31mError: �[39m SyntaxError: Unexpected token C in JSON at position 0
    at JSON.parse (<anonymous>)
�[90m    at parseJSONFromBytes (node:internal/deps/undici/undici:5584:19)�[39m
�[90m    at successSteps (node:internal/deps/undici/undici:5555:27)�[39m
�[90m    at fullyReadBody (node:internal/deps/undici/undici:1665:9)�[39m
�[90m    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)�[39m
�[90m    at async specConsumeBody (node:internal/deps/undici/undici:5564:7)�[39m
danger-results://tmp/danger-results-1c1dd4e8.json

Generated by 🚫 dangerJS against 0a4bf08