JITB-25: Formalize releases

[hark130]

I should likely be merging dev into main every time I complete support for a new Jackbox game (for now). I should also be updating the repo README.md (because it's no longer entirely accurate). Even better, I should devise a release checklist. Even better still... what happened to my "release jitb as a wheel" backlog ticket. (This might be it, now) I should start a CHANGELOG as well. Don't forget about jitb dependencies.

Acceptance Criteria:

• There's a formal release checklist on the wiki
• README updated
• CHANGELOG started
• devops code added to automate the release of jitb as a wheel
• Dependencies file added to the project
• Top-level package __init__.py contains adequate usage instructions

[hark130]

I didn't add any devops code but the file comment block in the pyproject.toml is good enough.