Description of problem:
CoCo infrastructure should provide a timeout for each command to prevent entities to be locked forever.
The behavior should be a bit similar to how it is being dome with asyncTasks.

There should be a parameter in the base parameter command that should be initialized every time with the default timeout, so the user will also be able to override it for specific operations.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Failed delete operations might make the client (CoCo) poll every time to check if the entity still exists 
2.
3.

Actual results:
The entity will be locked forever, since the delete will never happen

Expected results:
We should have a time out (or number of tries) that when this limit reached the entity will leave the lock state and present a failure event log

Additional info: