Implement duplex communication between HMI and RAI Agents

[boczekbartek]

Is your feature request related to a problem? Please describe.
Currently, communication of the task between RAI and HMI has some limitations:

1. it goes in 1 direction (HMI -> RAI)
2. is based on the ros2 topic -> no task start ack
3. The robot can't return task status, ask for task details or

Describe the solution you'd like
Implementation would solve the issues above by implementing 2 ros2 actions:

1. Task action:
   • HMI submits tasks to the robotic agent (~RAI agent) using ros2 action.
   • RAI agent accepts the task, frequently sends task feedback, and share the result at the end
2. Task feedback action: (probably better name needed)
   • RAI agent while executing the task can ask the HMI agent for more information about the task using another ros2 action

Describe alternatives you've considered

• ros2 service, but decided to use actions since we need feedback and the response can take long. For tasks - execution might be long. For feedback - the agent might be in the middle of a conversation.

Additional context

• HMI part is started by @maciejmajek in refactor: HMI Node  #143 and described in Refactor Human-Machine-Interface #142
• design heavily contributed by @maciejmajek

Status

• refactor: text hmi and implement hmi task as ros2 action #176
• feat(rai_node): execute mission as ros2 action #208
• implement mission feedback
• feat(text_hmi): toggle old messages in history #205

[rachwalk]

I think this issue has become stale, and can be closed (or should be reformulated). Please confirm @boczekbartek

[boczekbartek]

@rachwalk this issue was resolved in #208. Thank you for noticing!