Study: Define model for CM-Handle Connectivity State

Define a new cmhandle state to cater for scenario when connectivity is lost between NCMP and the device.  During this time it is not possible to determine the true state of the cmhandle or any data associated with the cmhandle.  

What might trigger a cmhandle to go to STALE?

1. dmi plugin identifies that the device is no longer contactable
2. dmi plugin identifies that an underlying device manager managing the device (node) is out of sync with the device itself. 

state : {
    cmhandleState   : CmHandleState,
    trustLevel      : ENUM (NONE, COMPLETE)
    lockReason      : LockReason,
    dataSyncEnabled : boolean,
    dataSyncState   : DataStoreSyncState
}

enum CmHandleState : {
     ADVISED,
     READY,
     LOCKED,
     DELETING,
     DELETED  # virtual state
}

There may be many reasons to trigger the trustLevel to change.  The table below reflects potential reasons

For now the scope of this story is to define the model and limit it to the following states :

   NONE : representing zero trust in the cmhandle state.  For example if the node is gone unsynched or EMS connectivity is lost

   COMPLETE : representing full trust in the data

In the future additional trust levels may be added as needed.