fix: missing errors in error mapper

[LinHuiqing]

Problem

The errors AttachmentTooLargeError and InvalidFileExtensionError were missing from the error mapper used for storage mode submissions. This caused them to throw 500 unknown route errors. This is an example trace of presenting this issue.

Solution

Breaking Changes

• No - this PR is backwards compatible

Bug Fixes:

• AttachmentTooLargeError and InvalidFileExtensionError errors added to error mappers to be treated like other form submission errors where validation fails. There should be a 400 status code returned and an error message asking them to try again. These 2 were the missing error mappings identified from possible errors from src/app/modules/submission/encrypt-submission/encrypt-submission.middleware.ts > validateStorageSubmission.

Tests

• Go to a storage mode form with at least 1 attachment field.
• Open the network panel.
• Make a submission with at least 1 attachment.
• Copy the cURL request of the above submission.
• In a terminal, paste this request and remove the file extensions in both the answer and the file field at the end. This is to simulate an invalid file extension (since there will be no file extensions).
• Add the -I flag to the cURL request.
• Enter the request. The status code should be 400 and the message should be "There is something wrong with your form submission. Please check your responses and try again. If the problem persists, please refresh the page."

[LinHuiqing]

Linear ticket: FRM-1437