robot_activity transition services should use std_srvs/Trigger instead of std_srvs/Empty

[asiron]

As sometimes, calling robot_activity services such as /start or /reconfigure/ can fail, e.g. no path to desired state, current state is the goal state, or transition has failed #2 , then std_srvs/Trigger makes more sense as it can indicate message, why it has failed.