A fancier way of dealing with mixed Zenodo DOIs.

[zaneselvans]

PR Overview

I tried creating a ZenodoDOI class that knows how to manage both sandbox and production archives. It works fine, but in the end seemed like it had too many little tentacles that touched other things in other places. But maybe there's a way to make it feel cleaner and simpler?

PR Checklist

• Merge the most recent version of the branch you are merging into (probably dev).
• All CI checks are passing. Run tests locally to debug failures
• Make sure you've included good docstrings.
• For major data coverage & analysis changes, run data validation tests
• Include unit tests for new functions and classes.
• Defensive data quality/sanity checks in analyses & data processing functions.
• Update the release notes and reference reference the PR and related issues.
• Do your own explanatory review of the PR to help the reviewer understand what's going on and identify issues preemptively.

[zaneselvans]

I think I'll close this for now in favor of the more limited changes made in #2798