Map Lifecycle State of a workcell orchestrator to it's WorkcellState #119
Description
Currently the workcell orchestrator which is a Lifecycle Node publishes a WorkcellState message whenever an event related to processing a task occurs. But this happens only when the node is in "active" lifecycle state.
Hence, to know the state of the workcell, once needs to query both it's lifecycle state and it's WorkcellState if active.
Starting a discussion on how we can consolidate the different states.
One way would be to extend the WorkcellState enums to include lifecycle states. Then have the workcell orchestrator publish the WorkcellState upon lifecycle transition events as well. It somewhat goes against the idea that publishers will be active only when the node is in active state but we can activate this publisher on_init().