[Access] Design error handling for web socket connection

[Guitarheroua]

Develop a comprehensive error-handling strategy for WebSocket connections.

Requirements:

1. Error Analysis:

   • Identify potential errors in the web socket controller and data providers.
   • Categorize errors into types such as:
     • Internal: Errors that should be logged but not exposed to users.
     • User-Reported: Errors that should be communicated back to the user.
     • Critical: Errors requiring immediate action, such as terminating the WebSocket connection.

2. Error Handling:

   • Design a system to handle errors, ensuring consistent behaviour across the controller.
   • Define clear rules for:
     • Sending errors back to the user.
     • Logging internal errors.
     • Dropping the WebSocket connection in critical scenarios.

3. Integration:

   • Ensure the error-handling mechanism integrates seamlessly with both the web socket controller and its associated data providers.

[Guitarheroua]

WS connection close handler should be part of the error handling design. See https://github.com/onflow/flow-go/pull/6750/files#r1853825821