In-memory data values may get occasionally reverted by watch event

This Jira is there to simply monitor a case scenario where the data model may get out of sync due to conflicting changes made by the core and the watch mechanism.

In the data model, KV watches are activated for devices that are currently in-memory.  If a core updates a device in the KV store, the watch gets activated for any core that has that device in-memory.  When the watch event is processed, it first check if another operation is currently in progress for that same device.  If so, it moves on.  Otherwise, it applies the content of the watch event to memory.  

There have been occasional cases where the event was carrying data that was already outdated when it got applied to memory and essentially reverted the device to an older value/state.  From this point on, the impacted device is out of sync.