What

1. Separate model-sync from Registration. ie. just persist the cm handle data with state 'ADVISED'
   This was accidently done before and the reverted here: https://gerrit.onap.org/r/c/cps/+/129102/6..9 so this link might help you where it needs to be added
2. Add logic to persist cm-handle with 'ADVISED' state once registration is successful
3. watch out for method names stil assuming sync will happen immediately
   1. e.g. org.onap.cps.ncmp.api.NetworkCmProxyDataService#updateDmiRegistrationAndSyncModule
4. CSIT test will be impacted as sync does NOT happen immediately anymore
   1. remove assert on module info (can be re-added on sync-on-command)

A/C

1. Demo
   1. after registration all CmHandles are in state 'ADVISED' (need to delay Watchdog possibly)
   2. after some time CmHandles states should move to 'READY'
   3. NFP-Operational should not be done as part of registration, but during watchdog process. 

Open Issues

1. Does updating cm-handles affect the cm-handle state. 
   Not for now. maybe later we have 'upgrade' or similar
2. Is the state always going to be persisted as 'ADVISED'?
   Yes for registration it always will be "ADVISED" for newly created cm-handles

Out of Scope