[Other]: RedisConsumerHandler created a BUG conversationID

[zhaolibo1989]

What would you like to share?

Review this func:
https://github.com/openimsdk/open-im-server/blob/v3.8.0/internal/msgtransfer/online_history_msg_handler.go#L93

storageMsgList, notStorageMsgList, storageNotificationList, notStorageNotificationList := och.categorizeMessageLists(ctxMessages)
conversationIDMsg := msgprocessor.GetChatConversationIDByMsg(ctxMessages[0].message)
conversationIDNotification := msgprocessor.GetNotificationConversationIDByMsg(ctxMessages[0].message)
och.handleMsg(ctx, val.Key(), conversationIDMsg, storageMsgList, notStorageMsgList)
och.handleNotification(ctx, val.Key(), conversationIDNotification, storageNotificationList, notStorageNotificationList)

This is a test case, the data is intentionally set and may occur. "32499" is user, and "openIMAdmin" is manager.

len(ctxMessages) = 2
ctxMessages[0] = Msg{sendID:"32499", recvID:"openIMAdmin", sessionType:4, contentType:2200(HasReadReceipt), ...}
ctxMessages[1] = Msg{sendID:"openIMAdmin", recvID:"32499", sessionType:4, contentType:1400(OANotification), ...}
storageMsgList = {ctxMessages[1]}
storageNotificationList = {ctxMessages[0]}

In fact, it has already happened in my debugging environment. To simplify, I only described the key data.

Based on the data above, we expected to get a chat conversation "sn_openIMAdmin_32499" and a notification conversation "n_32499_openIMAdmin," but that is not the result. Actally, that add an abnormal conversation with conversionID = sn_32499_openIMAdmin to the database. After that, the SDK will also have an additional abnormal conversation. Finally, the APP will display two conversations with the same userID openIMAdmin but different conversations sn_32499_openIMAdmin and sn_openIMAdmin_32499.

It is regrettable that I have not yet found an elegant solution.

Additional information

No response