Package Blossom as a wheel

[TheLonelyGhost]

We have an established pattern for deployment and in-place upgrades with the tor bots, there's no reason Blossom can't also follow that pattern.

If we were to take it as-is, manage.py would be at the base of site-packages/ in a virtualenv and would conflict with any other Django installation in that virtualenv. Other issues point toward a placing Blossom's code under a module acting as a namespace. Perhaps that module might be named blossom...

• [ ] Position all python modules under a namespace module
• [ ] Have pyproject.toml expose equivalent to manage.py as a console script. Document basic usage.
• [ ] Adapt GitHub Actions (see tor and other bots) to publish a wheel when tag is pushed to repo

[TheLonelyGhost]

Meh, given we're deploying Blossom in a way that requires git to be present, and given Django projects generally expect to be plastered into place from source code instead of packaged like any other python library, I'm gonna say this is non-essential.