[Webservice] Use AW status on myMdC for warnings that prevent launching correction

Description

We're already using the AW status if e.g. one detector is corrected successfully and another isn't. But if we can't launch any corrections, there are a couple of warning cases we currently report to myMdC as errors:

• If we can't see any detectors needing correction in the run folder
• If we're skipping correction on a dark run

There's also a CONFIG_NOT_FOUND message with a WARN prefix, but it's not used anywhere.

In theory, both of these cases are totally fine and not a cause for concern. But if they occur unexpectedly, it might be that the DAQ is misconfigured, and there might be data that's missing compared to what people expect.

How Has This Been Tested?

TBD

Types of changes

• Bug fix (non-breaking change which fixes an issue)

Checklist:

• My code follows the code style of this project.

Reviewers

@schmidtp @ahmedk

webservice/webservice.py

@@ -770,9 +770,11 @@ async def update_mdc_status(mdc: MetadataClient, action: str,
     Further informations are available at:
     https://git.xfel.eu/gitlab/detectors/pycalibration/wikis/MyMDC-Communication
     """
-    if message.split(':')[0] in ('FAILED', 'WARN'):  # Errors
+    if message.startswith('FAILED:'):
         flag = 'E'
-    elif message.split(':')[0] == 'SUCCESS':  # Success
+    elif message.startswith('WARN:'):
+        flag = 'AW' if action == 'correct' else 'E'
+    elif message.startswith('SUCCESS:'):
         flag = 'IP'
         if 'Uploaded' in message or 'Finished' in message:
             flag = 'A' if action == 'correct' else 'F'