Release workflows & `cargo binstall` support

We need release workflows for:
- [ ] `fontheight` (published to crates.io)
- [ ] `fontheight-cli` (published to crates.io and maybe PyPI)
- Support for `cargo binstall` would be a nice bonus to have and relatively easy if we get release artifacts set up anyway
- [ ] `static-lang-word-lists` (published to crates.io)
- [x] ~~`fontheight-wheel` (published to PyPI`)~~

We'll probably follow a tag naming convention to trigger releases, e.g. tagging `fontheight-v1.0.0` would release v1.0.0 of `fontheight`. Multiple tags can be applied to a single commit where it makes sense to do so

Alternatively, we could consider 3rd party release management tools

There's also the question of who should have ownership of the crates/wheels and getting the auth secrets set up