Updated code better handle malware scan errors so that endusers can b…

[tomshag]

…e better informed about their upload results.

#409

Description

Previously uploaded files that have Malware issues would have their final status set to "Purged".
This change will ensure that files with Malware detected will have final status "Failed", with the Failed status and the extended MalwareScan result returned when using the LegacyFileStatus request.

I've also changed the Final status for files that have completed the Broker User Story to "Purged" rather than "Deleted", to communicate that the Altinn Broker system has purged the file from its system.

Added a Unit Test that includes malware result update of file. This creates a somewhat incorrect status history as the file status will be automatically set to published before being Failed, but that should not occur outside of the Unit Tests, and status history is not returned by Legacy requests anyway.

Related Issue(s)

• Handling of Virus-scan result in Altinn 3 for Status in Altinn 3 and Altinn 2 #409

Verification

• Your code builds clean without any errors or warnings
• Manual testing done (required)
• Relevant automated test added (if you find this hard, leave it and we'll help out)
• All tests run green

Documentation

• User documentation is updated with a separate linked PR in altinn-studio-docs. (if applicable)

[Ceredron]

Looks good!
Should do a full repository search for "delete" and determine if it should change to "purge" to make sure we update all references.
Also need to update documentation, both the OpenAPI spec here and in altinn-studio-docs.

Also dotnet format.

[RagnarFatland]

Looks good to me!