Determine a clean fix for the factoid key duplication error

[ajax146]

This fix should not require databases changes.

I ran into an error processing your command: Command raised an exception: UniqueViolationError: duplicate key value violates unique constraint "factoids_pkey"
DETAIL: Key (factoid_id)=(445) already exists.

[Cpt-Dingus]

I don't think this is fixable since the id is handled by gino, either way a dev environment can't repro this

[ajax146]

Everything is always fixable, and this is 100% reproducible in a dev environment. It came in prod only by manual modification of the database, so that's how it would have to be reproduced.

I suspect this could be a bigger or more noticeable problem after #16 is implemented, and potentially more after #482 and all the tables have to be recreated

The running value of the primary key is stored in postgres. There has to be a way to set/modify it, whether that uses gino or something else