Automate Zenodo archiving

[jdangerx]

This issue tracks all the tasks required to get our automated archiving system up and running.

Scope

• Archivers create a report describing what happened during an archiving run.
• Each archiver can specify dataset-specific success/failure criteria.
• Archivers are robust to transient networking issues (false "failures" that are external to the data).
• Scheduled archiving runs produce a persistent record of their outcome (probably a GitHub issue).
• Scheduled archiving runs notify us of their outcome (Slack notification + issue assignment).
• All working archivers are being run on a schedule, publishing new archives to the production Zenodo site.

Out of Scope

• 68

• 31

• 44

• 43

- [ ] #77 
- [ ] #79 
- [x] Add production credentials to workflow
- [ ] #73 
- [ ] #75 
- [ ] #76 
- [ ] #74 
- [ ] #60
- [ ] #70 
- [ ] https://github.com/catalyst-cooperative/pudl-archiver/issues/80
- [ ] https://github.com/catalyst-cooperative/pudl-archiver/issues/81
- [ ] https://github.com/catalyst-cooperative/pudl-archiver/issues/144
- [ ] https://github.com/catalyst-cooperative/pudl-archiver/issues/276

[e-belfer]

@zaneselvans Do we feel satisfied closing this? We've changed the scope to move away from per-archive conditions since we originally wrote this, but I've closed #276

[zaneselvans]

It seems like the base level "automate" is done, and we could probably gather together various other issues that improve the validation of archives and any archiving bugs we run into.

Can we close the bugs that are listed here now, since they don't seem to have been causing issues? I guess that's just #74 & #81. We should figure out how we want to deal with drafts and continue to make the success/failure conditions more robust.