fix:race condition in db tracking module

[cunla]

fix #496

[Copilot]

Pull request overview

This PR attempts to fix a race condition in the DbTrackingModule where concurrent tracking events for the same message ID can cause duplicate key violations in the database. The fix wraps the persist method's logic in a synchronized(msg) block to provide mutual exclusion.

Changes:

• Added synchronized block around the database persistence logic in DbTrackingModule.persist() method

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[uhurusurfa]

It would be much simpler to just synchronize the entire method by adding synchronize to the method signature.
Although this blocks all threads even if they are trying to log a different message ID, this is a short term solution until the next major release and the performance cost is the same as the mechanism you have used which uses the concurrent hashmap since it will block all threads as well but adds the cost of managing a concurrent hashmap.

[uhurusurfa]

🚀 Thanks for the fix