Deploy workflow

[kaitj]

Proposed changes

Sets up the workflow for deploying DBSC (i.e. create release & push docker container). Also adds in some badges (e.g. Python version supported, etc.) - some of these won't work until a release is actually created. Would also like to a zenodo badge once released.

Ideally we would have a name determined before releasing.

Resolves #5 and #6.

Types of changes

What types of changes does your code introduce? Put an x in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionalitiy)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Other (if none of the other choices apply)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you are unsure about any of the choices, don't hesitate to ask!

• Changes have been tested to ensure that fix is effective or that a feature works.
• Changes pass the unit tests
• Code has been run through the poe quality task
• I have included necessary documentation or comments (as necessary)
• Any dependent changes have been merged and published

Notes

All PRs will undergo the unit testing before being reviewed. You may be requested to explain or make additional changes before the PR is accepted.

[kaitj]

This PR should be reviewed + merged prior to release.

[tkkuehn]

Needs a merge from rename-package