Expose simplified 'external' lock reason enum state over REST interface

Although internal we might need more enum values for 'LOCKED_MISBEHAVING' we dont want/need to expose such value to the external clients (and impacting those clients with future new states)

The simplest approach is in the REST layer to map the (internal) current cm-handle state to a new Rest(?)CmHandleState (open to better name suggestions!)

 Want Now:

Future?:

THis user story is to implement such a map in the NCMP Rest Layer

A/C:
If module sync fails see LOCKED_MODULE_SYNC_FAILED in db LOCKED_MISBEHAVING in payload
Are enums documented? Document in openapi description of LOCKED_MISBEHAVING enum
Only have LOCKED_MODULE_SYNC_FAILED

Out of scope:
Service layer not altered