Improve pre-mission checks and alerts

[prasm313]

Describe the improvement you would like to see

Mission pre-checks

• Should implement all backend checks (offline, pressure, battery) in one function (all endpoints should use the same function) #1491 Add a common mission pre-check function #1602
• Have a discussion whether the pre-check should be done in frontend or backend
• Should have a backend pre-check for high pressure, not just low pressure (Add a common mission pre-check function #1602 )
• Should not be able to schedule a mission when the robot has connection issues Add offline and isarConnected prechecks #1620
• When a robot is running on Deck1 you should not be able to schedule a mission on Deck2 (Echo missions). #1522
• Should remove possibility to rerun a "Return to home" and "Localization" mission. (today you get a alert banner "Failed to rerun mission") Remove rerun button for localization and return to home missions #1603

Alerts

• UX for user alerts and notifications, see comment
  • Only generate banner alerts for specific alerts. Generate list alerts for all alert.
  • Create alerts page.
  • Create functionality for silencing alerts, removing the "red dot" under the alerts icon when there are no new alerts.
• Store alerts and alert timestamps
• Implement remaining alert types
  • Aborted missions
  • Low battery
  • Low pressure
• Implement alert feature #1560 - In order to improve user clarity
  • Implement alert list feature #1713 - Frontend dropdown alerts menu, no change to alert behaviors.
  • Create a timestamp showing how old the alerts are in the front end and sort list alerts with newest first.
  • Make it so notifications are not overwritten when a new one is generated.
  • Make alerts persistent and do not disappear on page refresh for a defined time. I.e. currently "Request error" alerts disappear on page refresh.
  • Failed missions banner don't pop up or update when missions fail #1724
• Update message in robot-is-blocked banner #1523 - Change text for blocked error banner

How will this change existing functionality?

Will make Flotilla easier to navigate for the users.

How will this improvement affect the current Threat Model?

N/A

[haakonsf]

Edited text to reflect current identified gaps for a well working alerts feature. #1713 provides the implementation of a notifications drop down menu, but does not change alerts behavior. With this alerts are generated twice in order to not remove any current functionality. This is temporary until a discussion on desired notification behavior and what alerts to display when is had.

[haakonsf]

From a previous UX discussion:

[aeshub]

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

[Eddasol]

Most of this is solved or covered by #1836. Low battery is showed on robot card, so to prevent information overload this will not be implemented as an alert unless users request it. Will close.