Isar mission run sometimes is not yet created when receiving task status

[andchiind]

Describe the bug
In the screenshot, the LogWarning line is sometimes reached. This is likely due to the mission run not being updated in the database at the point in time when the first task update is received from ISAR, causing it to not find the mission run. This causes it to send a value of null to signalR, in turn causing an error in the frontend. This should be handled better, and at the very least we should not send a null value for the mission run to the frontend.

To Reproduce
Running missions with isar_robot where the first task finishes quickly.

Expected behavior
The mission run value sent to signalR should never be null.

Screenshots

[aeshub]

This issue has automatically been marked as stale as there has been no activity for 60 days.