Rework busy lock when allocating id's

Messages from Koby and Peri:

Koby:

Another thought here - even if we fix the root cause, I think we must remove this busy loop. This totally breaks the system when occurring
Peri:

Looks like this issue occurred when an idKey is not unlocked accidentally in IdManager which leads to LockManager#lock goes into busy spin. But this is a corner case due to a bug.

We could avoid it by thread wait/notify by Async Clustered DTCN on lock (since lock is stored in MD-SAL), upon remove DCN, waiting threads can be notified for the particular lock. Not sure its worth to do it now and should be done as an enhancement since it needs more testing effort.