Repo improvements

[gaieges]

Jotting down some things here that we should come back to for OSS repo posterity

• Improved comments that meet our standards in manifest / models content
• Smaller base docker image (can probably use alpine now that we dont need the web3 stuff)
• Travis CI autotest and pypi deploy on merge / tag
• "How to use" documentation for outsiders
• Tweaks to readme: (no more venv, now pipenv)
• Rename python module (basemodels -> hmt-basemodels or something along those lines) and break out per component (Manifest, RequestConfig, etc)

[Villux]

Should travis handle pypi deploy? Latest version 0.0.6 was not in pypi.

[Villux]

Most likely the reason was missing tag 0.0.6

[gaieges]

Yep, see here @Villux https://github.com/hCaptcha/hmt-basemodels#note-for-maintainers-deploying-to-pypi

[pared-imi]

It seems like currently there is no build that would automatically deploy to pypi.
The latest build on Travis is from a year ago.
@Villux

1. Is there any reason to not deploy on a tag event?
2. Are we interested in reactivating this?
3. If so, should we do it with GitHub actions? When discussing with @e271828- I understood that at some point we wanted to migrate to GitHub Actions.

If we are interested in this I could tackle it, but I would need security credentials set in the repo settings, to which I do not have access.

[Villux]

hmm no idea anymore on this package. I think we can follow the best practices that eng team has created. I work for ML so I don't know them exactly. Let me know if you need more help