FIX: adds error handler and retry to connection state request

[pedroanastacio]

Description

• The socket server is restarting too frequently in production. This adjustment is an attempted solution, as an unhandled request was found that would crash the socket server if the API returned an error.

Summary

• Adds error handler to connection state request
• Adds retry logic to connection state request if API return an 5xx error.

Checklist

• I reviewed my PR code before submitting
• I ensured that the implementation is working correctly and did not impact other parts of the app
• I mentioned the PR link in the task

[guimroque]

Code Review - Summary

What was done

• Added error handling to the CONNECTION_STATE socket event handler to prevent socket server crashes
• Implemented retry logic with exponential backoff for 5xx errors when requesting connection state from API
• Created a reusable retryWithBackoff utility function with proper TypeScript types and JSDoc documentation
• Added proper error logging with structured information (message, status, url)
• Ensured graceful fallback by emitting data: false when all retry attempts fail

Positive Points

• ✅ Addresses the root cause of socket server restarts by handling unhandled API errors
• ✅ Well-documented retryWithBackoff function with comprehensive JSDoc
• ✅ Proper error handling strategy: retry on 5xx errors, fail fast on client errors (4xx)
• ✅ Structured error logging with relevant context
• ✅ Exponential backoff with jitter to prevent thundering herd
• ✅ Graceful degradation - returns data: false instead of crashing
• ✅ TypeScript generics properly used for type safety
• ✅ Follows project naming conventions and code structure

Issues Found

• 1 important issue with file naming convention
• 1 suggestion for code organization improvement

Total comments: 2 (0 critical, 1 important, 1 suggestion)

[guimroque]

LGTM! ✅

Previous issues have been fixed. Code approved.