Editable inprogress jobs, remainder-based input, custom events

[smartin015]

This is a UX-heavy change aimed at #99, #101, and to some extent #9.

It breaks the prior invariant that for sets remaining + completed = count, allowing for users to override/pad the current run of a job allowing for front-loading work or re-printing failed items without having to mess with the overall job count.

Job repetition is also now specified using remaining instead of count, effectively removing the need for the user to think about the total number of runs of the job when desiring to pop off additional job prints.

Custom events are also included for #117, and temp files are filtered out of CPQ custom file analysis.

• Fix tests that assume Set tracking invariant (as above)
• Ensure behavior of LAN queue jobs is still consistent (i.e. uneditable, for now)
• Thoroughly test DB schema migration - multiple jobs, multiple sets with different states
• Fix job transfer-to-queue failing to remove old job from UI (but recovers on refresh)
• Collect early user feedback
• Show remainder gap in non-draft mode even if completion exceeds count