migrate to a more robust database solution

Handling database locks from conflicting components is slowing down the tweet scraping mechanism, which is damaging the ability of the app to perform trend detection. Need to swap out sqlite3 for a database engine that handles locking better. To consider:

* postgres
* mysql

Additionally: the title daemone is writing titles directly into the entities table at the moment. this means that even if I resolve database level locks, the title_daemon and scraper will still encounter locking conflicts when trying to write into the entities table. Should factor out titles into a separate table to eliminate table level locking conflicts.

Should consider swapping out raw SQL for SQLAlchemy to make swapping out backends easier.