Build+Deploy Python Wheels in CI

[jondo2010]

New and improved Python workflows for CI/dev/release:

• Python workflows are run for any PRs that touch python code. Wheels are built and spot-checked for Linux + Windows here.
• First the linter is run, and gates all the subsequent jobs as an early-fail
• For pushed tags and to main, the mac wheels are also built (these take 25-35 mins)
• For refs landing on main, i.e., a PR was merged, all the mac,windows,linux wheels are collected into a "development" release on GitHub.
• When a tag starting with "v", i.e, "v0.1.0" is pushed, a "tagged-release" job is run at the end that releases to GitHub and additionally to PyPI

Also:

• upgraded numpy, pyo3, maturin
• fixed the rerun entrypoint in pyproject.toml, so that after installing the wheel (or running just py-build), the rerun cmd is available on the CLI.

Closes #352

• Test the tagged-releases.
• Need to put PYPI_PASSWORD in the GH secrets section.
• Pre-launch: Switch the GH secrets and repo to use pypi instead of testpypi

Checklist

• I have read and agree to Contributor Guide and the Code of Conduct
• I've included a screenshot or gif (if applicable)
• I've added a line to CHANGELOG.md (if this is a big enough change to warrant it)

[emilk]

When a tag starting with "v", i.e, "v0.1.0" is pushed, a "tagged-release" job is run at the end that releases to GitHub and additionally to PyPI

Please update RELEASES.md to reflect this naming scheme!