Publish to PyPI

[bmaher]

One-line summary.

Closes #4.

Description

This PR:

• Allows for publishing to PyPI (manually currently).
• Updates the README to instruct downloading from PyPI.

Types of Changes

What types of changes does your code introduce? Keep the ones that apply:

• Bug fix (non-breaking change which fixes an issue)
• Configuration change
• Documentation / non-code

Review

Reviewers' checklist:

• If this PR implements new flows or changes existing ones, are there good tests for these flows? If this PR rather removes flows, are the obsolete tests removed as well?
• Is the documentation still up-to-date and exhaustive? This covers both technical (in source files) and functional (under docs/) documentation.
• Is the changelog updated?
• Does the new version number correspond to the actual changes from this PR? In doubt, refer to https://semver.org.

After this PR

Any follow-up action necessary?

[zincr[bot]]

🤖 zincr found 0 problems , 1 warning

ℹ️ Dependency Licensing
✅ Large Commits
✅ Specification

Details on how to resolve are provided below

---

Dependency Licensing

All dependencies specified in package manager files must be reviewed, banned dependency licenses will block the merge, all new dependencies introduced in this pull request will give a warning, but not block the merge

Please ensure that only dependencies with licenses compatible with the license of this project is included in the pull request.

• ℹ️ Detected pyyaml as a dependency in pyproject.toml, licensed under: MIT please review it and confirm you wish to introduce this to the codebase