Automate releases with release.yaml

[cisaacstern]

Currently:

• latest release according to pypi is 0.7.1
• latest tag on GitHub is v0.7.0
• latest release according to GitHub releases page is 0.6.1

🙃

This PR adds the same release.yaml as used in pangeo-forge-recipes to automate this process.

@yuvipanda, if this looks good to you, I can add a pypi token as a repo secret and cut a 0.8.0 release.

[codecov]

Codecov Report

Merging #80 (1c8ba25) into main (5b2faba) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #80   +/-   ##
=======================================
  Coverage   95.75%   95.75%           
=======================================
  Files          13       13           
  Lines         424      424           
=======================================
  Hits          406      406           
  Misses         18       18           

[yuvipanda]

@cisaacstern you can use pypi's trusted publisher instead, is easier! https://blog.pypi.org/posts/2023-04-20-introducing-trusted-publishers/

Feel free to self-merge once you set that up! Here's an example PR in another project: jupyterhub/jupyter-remote-desktop-proxy#46

[cisaacstern]

@yuvipanda thanks, didn't know about trusted publishing, it's great! Added that.

Pinging you for a quick re-review because I also changed a few other things to enable dynamic versioning... look okay to you?

[yuvipanda]

One comment about when to trigger, but otherwise if this works go for it! Thanks for taking care of it, @cisaacstern!

[yuvipanda]

Thanks for indulging me, @cisaacstern! Feel free to merge whenever you feel like