WebBrokerAPI: Guard channel reads with comma-ok pattern in WebBrokerApi receiver to prevent nil-message panics

[coderabbitai]

Summary

In event-gateway/gateway-runtime/internal/connectors/receiver/websocket/broker_api_connector.go, the channel receives in inboundLoop (around line 406) and outboundLoop (around line 465) use the plain form (msg := <-conn.inbound / msg := <-conn.outbound). When teardown closes these channels, the receive returns a zero/nil value and subsequent dereferences (e.g., msg.Value) can panic.

Proposed Fix

Apply the comma-ok pattern to both receive sites so the loops exit cleanly when the channel is closed:

// inboundLoop
case msg, ok := <-conn.inbound:
    if !ok || msg == nil {
        return
    }

// outboundLoop
case msg, ok := <-conn.outbound:
    if !ok || msg == nil {
        return
    }

References

• PR: Add implementation for WebBrokerAPIs #1954
• Review comment: Add implementation for WebBrokerAPIs #1954 (comment)

Raised by @senthuran16.