Adding two CI pipelines to ease release/deploy

[joseph-flinn]

Summary

Added two CI pipelines: 1) Build & Release, and 2) Publish to PyPI to ease in releasing this project.

Build & Release

This pipeline grabs the version from the setup.py file, builds the release assets and attaches them to the pipeline. It then checks to see if the version has been bumped and the current branch is master. If both of these are true, it creates a draft release and attaches the build assets to it.

There is a stub in this pipeline to add in the testing suite, but adding the dynamodb-local was something that I didn't have time to do.

Publish to PyPI

Once release notes have been added to the draft release and everything looks good, publishing the release will kick off the Publish pipeline. This grabs the release assets from the most recent release (the one that was just published) and then automatically submits the entire ./dist directory to PyPI. This will require a PIPY_API_TOKEN to be added to this repo under Settings => Secrets => Repository Secrets. Everything has been tested up to this point on my fork.

Notes

:warning: PIPY_API_TOKEN needs to be added to this repository's settings (see above)