Refactor Event Notification System

[takameyer]

Problem

In our React implementation, we have run into an issue that occurs when multiple write transactions occur in tandem that cause the hooks to update. The issue is that the hooks will reregister their event listeners when they detect a change, and that it is potentially possible to be in a new write transaction when this subscription occurs.

See issue #4375

Solution

We would like to implement a solution similar to what the .NET SDK has in place. This solution will have a single subscription on object store that will process a queue of listener callbacks registered in user space. This allows the SDK code to be able to detect if it is in the middle of a write transaction, and can then process the queue after the current transaction is committed or terminated.

This will make a more robust notification system that will not crash if a listener is added during a write transaction.

How important is this improvement for you?

Would be a major improvement