feat: sha256 hash of files and processed files

[insertish]

No description provided.

[Rushmore75]

Could you add some more information to this, so I could potentially work on it?

[insertish]

When a file is uploaded, the server should generate a sha256 hash of it and store it in the database.
If the file is further processed, the server should also generate a sha256 hash for the output (e.g. after stripping EXIF data from a file / reprocessing a video / etc -- can interject right before it's uploaded to s3).

To store the hashes, I would just use a string array on the File database model, e.g. hash?: string[].

[Rushmore75]

Trying to read the codebase that's already here - Whats the tag part of the routes for? / what does it do?

[amycatgirl]

tag corresponds to where the file will/is being used, for example

http://localhost:3000/attachments/1CXaLI6UcCYCRD2A5qI94RQL1lPf_egejPwAce5Xj5

attachments would be the tag of the file.