Update report on events

[aeshub]

Closes #212
Closes #144

[aeshub]

Not very happy about the "duplication" of StepType and InspectionType here but not certain what else to do.

[aeshub]

There is one issue which I'm uncertain how should be addressed.

When starting a mission in ISAR from Flotilla the response from ISAR contains the mission details which Flotilla then writes to the database as a Report object which contains IsarTask and IsarStep as lists. However, the state machine in ISAR has started executing the current mission before Flotilla has written to the database. Thus ISAR is sending status updates for mission, task and step which Flotilla will not recognize because it can't find those IDs in the database yet as the write operation is not complete.

Not entirely certain how this should be resolved.

[oysand]

There is one issue which I'm uncertain how should be addressed.

When starting a mission in ISAR from Flotilla the response from ISAR contains the mission details which Flotilla then writes to the database as a Report object which contains IsarTask and IsarStep as lists. However, the state machine in ISAR has started executing the current mission before Flotilla has written to the database. Thus ISAR is sending status updates for mission, task and step which Flotilla will not recognize because it can't find those IDs in the database yet as the write operation is not complete.

Not entirely certain how this should be resolved.

I think a better way to solve this issue is to move the misssion planner from ISAR to Flotilla so that Flotilla provides the mission to ISAR. That way we can toggle if ISAR should use a local mission planner or be used in combination with Flotilla. We can then write the mission to the database before sending it to ISAR

[aeshub]

There is one issue which I'm uncertain how should be addressed.
When starting a mission in ISAR from Flotilla the response from ISAR contains the mission details which Flotilla then writes to the database as a Report object which contains IsarTask and IsarStep as lists. However, the state machine in ISAR has started executing the current mission before Flotilla has written to the database. Thus ISAR is sending status updates for mission, task and step which Flotilla will not recognize because it can't find those IDs in the database yet as the write operation is not complete.
Not entirely certain how this should be resolved.

I think a better way to solve this issue is to move the misssion planner from ISAR to Flotilla so that Flotilla provides the mission to ISAR. That way we can toggle if ISAR should use a local mission planner or be used in combination with Flotilla. We can then write the mission to the database before sending it to ISAR

I have mentioned this in a new issue #226. It's easier to solve in a different PR and to just include this functionality as it is now. It works somewhat for turtlebot, but there are some unfortunate sideffects.

[GodVenn]

LGTM, just one renaming suggestion

[GodVenn]

Some naming suggestions for methods

[oysand]

LGTM

[GodVenn]

LGTM