A full release workflow

### Prerequisites

- [x] I have read [CONTRIBUTING.md](https://github.com/EFForg/rayhunter/blob/main/CONTRIBUTING.md)

### What problem does this feature solve or what does it enhance?

there are too many manual steps in the release process described in CONTRIBUTING.md:

1. the sed call there has been out of date many times, and it actually only works on macos right now (had to make changes to run it on ubuntu)
2. naming your own tag and pushing it is a lot

### Proposed Solution

release.yml workflow should cover the entire thing:

1. make a PR with the necessary changes
2. after approval, trigger another workflow to auto-merge and make the tag, push the tag automatically
3. make the github release (this is the part that already exists)

Not hellbent on this exact solution, but the more we can automate, the better

Whoever picks this up can fork the rayhunter repo onto their private account and manually test the workflow there.

### Alternatives Considered

no