Improve error handling: log instead of silently swallowing exceptions - #1

Summary

Multiple catch blocks across the WebSocket proxy layer were empty or used ignored — failures in forwarding messages, closing connections, and handling upstream errors were completely invisible. This makes debugging production issues nearly impossible.

Changes:

• NewBingGoGoClientWebSocket: All three empty/silent catch blocks now log with appropriate severity:

  // Before (onClose, onError): catch (IOException e) {}
  // After:
  catch (IOException e) {
      LOG.warn("Failed to close server WebSocket (code={}, reason={})", code, reason, e);
  }

• NewBingGoGoServerWebSocket: onException was closing the client silently; ping failures cancelled the task without any trace. Both now log WARN/ERROR.

• NewBingGoGoServer:

  • getReturnErrorWebSocket.onOpen(): catch (IOException ignored) → logs the failure
  • getReturnErrorWebSocket.onException(): was a no-op → now logs the error
  • goUrl() header copy: guards against null values (previously passed null to addRequestProperty)
  • goUrl() stream reading: handles missing Content-Length (-1) and premature EOF instead of looping on a negative length or writing -1 bytes

• Added private static final Logger LOG (SLF4J) to all three application classes for consistent structured logging.

All logging uses SLF4J (already a project dependency via slf4j-log4j12). No behavioral changes — just visibility into previously-silent failures."

Link to Devin session: https://app.devin.ai/sessions/712bf9af5b9541129150746b33b0f1dc
Requested by: @oneky