Persisted logs

[aaronleopold]

Digging through a, potentially massive, log file is really not ideal. Not only for troubleshooting, but if something were fail to be inserted I'd like an easily accessible way for a user to know immediately.

The current, basic log model in the prisma schema should be updated to have the following:

• [ ] Error kind (e.g. UnsupportedFileType, ImageIoError, ArchiveEmptyError, etc.)
• [ ] Job information (if available)
  • [ ] This will be a relation

All throughout the core, logic will need to be added to persist these logs to the DB instead of only logging to the log file as it currently does. Because that is a large undertaking, I am separating the interface aspects of this into a separate issue.