Add check for min pressure in robot when starting missions

[andchiind]

Closes #1019

There might be some smaller conflicts with #1279 to be merged, since I rewrote the update robot controller in order to implement this. This will need to use the new update service functions in that PR, if their interface changes.

[github-actions]

🔔 Changes in database folder detected 🔔
Do these changes require adding new migrations? 🤔 In that case follow these steps.
If you are uncertain, ask a database admin on the team 😄

[andchiind]

Here is what it looks like in the frontend:

[Eddasol]

This works if scheduling echo missions but not if scheduling missions trough inspection page or re-running a mission

[Eddasol]

It prevents the user from scheduling the mission when the pressure is too low, but queued missions will still begin. Should there be some check on that as well?

[andchiind]

It prevents the user from scheduling the mission when the pressure is too low, but queued missions will still begin. Should there be some check on that as well?

This would involve having a check in the queue event handler which cancels missions if the pressure is too low. In effect it would cancel all missions in the queue and then send an error to the frontend for each mission. It is possible but I think we may need to have further UX discussions before implementing this. The scope of this PR was to provide user feedback when scheduling missions.

[mrica-equinor]

LGTM :)