CI: Make Zenodo archival dependent on PyPI publish

[MattF-NSIDC]

Part of doing a release is publishing to PyPI and another part is archiving with Zenodo. Before one of those artifacts is there, we can't really say we've "released". Once either is published, we can't go back. Zenodo just zips up our source code, so it is not likely to fail, but what if PyPI publish fails? Currently, we would have a Zenodo release, so we'd have to do a patch bump to try PyPI again.

I think it makes sense to re-tag to resolve failed PyPI publishes, so it'd be better to have not already published to Zenodo. I ran in to that situation today, hence v0.6.1 :)

Currently, both PyPI publishes and Zenodo archival are triggered by GH Releases. I think we should change our triggers such that contributor tags -> PyPI builds -> contributor makes GH release -> Zenodo archives. If the failure is early, we can just try again by re-tagging.

[betolink]

What's the status of this one @MattF-NSIDC ?

[MattF-NSIDC]

0% progress :)