This pull request refactors the mutex usage in the socket modules to improve concurrency control and processing order for different event types. Instead of a single processingMutex, the code now uses dedicated mutexes for messages, receipts, notifications, and app state patches. This change enhances clarity, prevents resource contention, and allows more granular locking for each event type.

Concurrency and Mutex Refactoring:

• Replaced the single processingMutex with four dedicated mutexes: messageMutex, receiptMutex, appStatePatchMutex, and notificationMutex in src/Socket/chats.ts. Each mutex now ensures ordered processing for its respective event type.
• Updated all function signatures and exports in src/Socket/chats.ts, src/Socket/messages-recv.ts, and src/Socket/messages-send.ts to use the new mutexes instead of processingMutex. [1] [2] [3]

Event Processing Improvements:

• Changed event handlers in src/Socket/messages-recv.ts to use the appropriate mutex for receipts (receiptMutex), notifications (notificationMutex), and messages (messageMutex) to ensure each type is processed in order independently. [1] [2] [3]
• Updated app state patch processing in src/Socket/chats.ts to use appStatePatchMutex, ensuring app state patches are handled in order without blocking other event types.
• Modified message sending logic in src/Socket/messages-send.ts to use messageMutex for appending messages, improving isolation between message events.