Airlock - Handle malware scanning failed scans

[eladiw]

Description

As a TRE Developer
I want to be handle malware failed scans and move the request to failed
So that the researcher knows the request failed

Acceptance criteria

• Failed to scan for any reason should be catched by the airlock processor (e.g. password protected file / encrypted)
• move the request to failed state

[tanya-borisova]

The issue here is how to know there was a failed scan. E.g. password protected zip might cause a problem

[yuvalyaron]

#2395 might be useful as a reference

[yuvalyaron]

Password protected zip files result in "blocked by scanner" status - we should add the output of the the scanner to the "errorMessage" field that we have in AirlockRequest (we should rename errorMessage to statusMessage to make it more generic).

Files that are too big (>2GiB) are currently ignored by the scanner, and result in the request being stuck on "submit" - this should be addressed by the malware scanner team, as we currently don't have any indication that the request is invalid.