* Modify conversation_id index options
Removed the unique constraint from the conversation_id index.
* fix(msggateway): reset read deadline in pong handler to prevent Web client timeout
Root cause:
Due to browser API restrictions, Web (Wasm) clients cannot actively send standard WebSocket Ping frames. They rely entirely on server-initiated Pings (every 27s) and automatic browser Pong responses to maintain the connection. The `pongHandler` was empty and failed to reset the connection's read deadline upon receiving a Pong, causing the server's read loop to strictly time out at 30 seconds.
Solution:
Call `c.setReadDeadline()` inside the `pongHandler` to properly extend the connection's lifespan when a Pong frame is received.
---------
Co-authored-by: OpenIM-Gordon <1432970085@qq.com>
* fix: performance issues with Kafka caused by encapsulating the MQ interface
* fix: admin token in standalone mode
* fix: full id version
* fix: resolve deadlock in cache eviction and improve GetBatch implementation
* refactor: replace LongConn with ClientConn interface and simplify message handling
* refactor: replace LongConn with ClientConn interface and simplify message handling
