Fixed bug introduced in 0745cb3cdd in events.py

Hello Severin ;-)
adding uuid for each robot action
changing logging parameters to show both name and id.
passing future and action name and id to the fn function which is lockawarefn in decorators.py. action name is needed in printing the logs and future is needed for setting a flag showing when the action is started.
change the place of the chunk to make the log more readable. In this order every action is first added to its parent and then other log information is written regarding to that action.
changing the lockawarefn so that it accepts future and action name as input to use them in calling set_acquired of future and using name containing action id for logging.
change logging so that id and name of each action is recorded instead of name
{getabspose->get} (fixes d304b45cb3c)
{set_acquired->acquired_resource} (fix d3820a75817054f)
Uninitiliazed variable