Delayed update of device object on non-owning core

When a device is created, it is assigned to and owned by a specific core.  The non-owning core will store details of that device in-memory.

When a request to enable the device is issued, the owning core will complete the request.  The non-owning core should receive updates that the device has been enabled through the watch mechanism.  Unfortunately, the information received is being stored in the wrong "node" of the revision tree.  This causes the non-owning core to stay in a looping state until a DATA_REFRESH_TIMEOUT is reached and forcing the non-owning core to pull the latest information from the db and storing the information in the correct "node".