INT B-20928

[danieljordan-caci]

Agility ticket

Summary

Security wanted us to not use MD5 hashing, so transitioning to SHA256 for uploads and adding in the CheckSumAlgorithem when uploading to S3.

This also contains code to fix some flaky tests. Idk, man.

How to test

1. You'll need to go to your .envrc and uncomment export STORAGE_BACKEND=s3
2. Run direnv allow
3. Run aws-vault exec transcom-gov-dev -- make server_run
4. While that's building, make sure you are in the right AWS profile - transcom-gov-dev
5. This allows us to upload files to S3 instead of locally (docs here)
6. Log in as a customer, fill out all information and upload some orders
7. In your CLI, run aws-vault login transcom-gov-dev - this will open the AWS Console
8. Search for S3 and get in there
9. Find your buckets
10. There should be one that says transcom-gov-dev-app-devlocal-us-gov-west-1, click it
11. You should see your name/repo if the file uploaded correctly (ex. daniel.jordan_cn)
12. Click through and click the file you uploaded to where you see the Object Overview section
13. Scroll down and you should see an Additional checksums section
14. Confirm you see an additional SHA-256 checksum

Screenshots

[lucyluuuu]

Did not see new vulnerabilities on files changed when scanned locally. Pre-test jobs ran successfully.