fix Client failed to withdraw the message

[adpanru]

🅰 Please add the issue ID after "Fixes #"

Fixes #3241

Problem Description
Users were unable to revoke messages, with the server returning error code 1004 (RecordNotFoundError) and the message "msg not found".
Investigation Process
Log Analysis:
Message sending and push operations were successful, with normal log records
During revocation attempts, the error "Error: 1004 RecordNotFoundError msg not found" was returned
Data Consistency Verification:
The conversation API query showed that the maximum sequence number (maxSeq) was 399
However, the message attempting to be revoked had a sequence number of 561
This indicated an inconsistency between database state and actually sent messages
Root Cause:
Messages were successfully sent and pushed to online users but failed to be persisted in MongoDB storage
The conversation sequence number records were not properly updated
When attempting to revoke, the system could not find the message record with the corresponding sequence number
Fix Solution
Design Approach
Implement a fault-tolerant mechanism that allows message revocation to proceed under specific conditions, even when the message record cannot be found.
Implementation Details
Modify the RevokeMsg method in internal/rpc/msg/revoke.go:
Instead of immediately returning an error when a message doesn't exist, implement a fallback strategy
Verify that the sequence number is within a reasonable range
Create a temporary message object for revocation notification
Log warnings but allow the operation to continue
Add Helper Function:
Implement getSessionTypeFromConversationID method to infer session type from conversation ID
Identify single chat or group chat types through prefixes (e.g., "sp_", "sg_")

[github-actions]

🤖 All Contributors have signed the CLA.
The signed information is recorded here
_{Posted by the CLA Assistant Lite bot.}

[adpanru]

I have read the CLA Document and I hereby sign the CLA