Allow echo missions with tags that do not have an area

[aeshub]

Describe the improvement you would like to see
There is currently a check on the tags that are in Echo missions when we retrieve them from Echo/STID which means it is not displayed in the frontend as available if less than half of the tags have an area. This area is then mainly used to identify which deck the mission should be in and which map to select for the mission.

We currently have issues where all of the tags in a mission does not have an area (for example pipes crossing multiple areas) and we would like to run those missions anyway. It should be possible to run a request to Echo and add the mission definition and then maybe add the area afterwards if it has to be there.

How will this change existing functionality?
Missions are very focused on areas now and not having an area means not having a deck. Currently we can go across all areas in this facility whereas that might not be true in other places with different types of robots.

How will this improvement affect the current Threat Model?
Keep in mind the risk of running missions without an area with robots not able to cross between different areas.

[tsundvoll]

Suggestion to remove the check that hinders missions with tags without area