Improve build and automate push to PyPI

[millerdev]

The version number has been bumped to 2.3.0. A dev version will be pushed to PyPI when this PR is merged, and the final production version of 2.3.0 will be pushed when a new tag is pushed with the value v2.3.0.

🐡 Review by commit.

Process for testing build and publish to PyPI

Update pypi.org as necessary to allow publish from Github Actions.

Temporarily rename/overwrite a workflow that exists on the master branch. The gh workflow run command cannot run workflows that do not exist on the primary branch.

git mv `.github/workflows/{pypi,tests}.yml
git commit -m "DO NOT MERGE temporary commit for testing pypi.yml"
git push && gh workflow run tests.yml --ref dm/auto-pypi

Adjust tests.yml as necessary, push changes, and repeat the last command until successful publish is achieved. Then rebase and update pypi.yml with the final good version of the temporary tests.yml.

Based on SO answer.

[gherceg]

Oh just noticed the "This branch had an error being deployed" message. Seems like resolving that before merging is correct?

[millerdev]

I think that error was a result of earlier PyPI publication testing in Github Actions, which should be resolved with the force push of d498e56. Notice that it says both are outdated:

1 failed (outdated) and 1 active (outdated) deployments

I'm going to merge and see if the dev release successfully makes it to PyPI. If not, I'll fix the issue before pushing a final version tag.

[millerdev]

Forgot to mention in the description that a major change introduced by this PR is that Linux wheels are built and published to PyPI for all sported Python versions. These are "manylinux" wheels built using cibuildwheel.

Previously (in practice) only a single wheel was built/published using whatever version of Python was installed by the person doing the publishing.