Reassess error messages referring to an invalid mission code

[tangobravo62]

After implementation of the access right functionality the mission context is known for the backend services. At this time the error messages should be checked, whether references to a possibly invalid mission code can be removed, e. g. in the following case:

prosEO (NM4T)> product create
Checking for missing mandatory attributes ...
Product class (empty field cancels): TEST
File class (empty field cancels): TEST
Sensing start time (empty field cancels): 2020-09-10T12:30:00.123456
Sensing stop time (empty field cancels): 2020-09-10T14:30:00.123456
Product generation time (empty field cancels): 2020-09-10T14:32:00.123456
(E2960) Product data invalid (cause: 400 199 proseo-ingestor (E2012) Mission code NM4T and/or product type TEST invalid)

Since the user must be logged in to the mission NM4T, the error is clearly with the product type.

[tangobravo62]

Messages cleaned up (only Ingestor affected):

prosEO (PTM)> product create
Checking for missing mandatory attributes ...
Product class (empty field cancels): TEST
File class (empty field cancels): TEST
Sensing start time (empty field cancels): 2020-09-10T12:30:00.123456
Sensing stop time (empty field cancels): 2020-09-10T14:30:00.123456
Product generation time (empty field cancels): 2020-09-10T14:32:00.123456
(E2960) Product data invalid (cause: (E2012) Product type TEST invalid)