Update harvest DB tables

[rshewitt]

User Story

In order to use the most recent table definitions, datagov wants to update the harvest database tables to reflect what's in the table definition document

Acceptance Criteria

[ACs should be clearly demoable/verifiable whenever possible. Try specifying them using BDD.]

• [ ] GIVEN the existing db models in harvesting logic \ WHEN an update to the model happens \ THEN the new table(s) should exist as they are in the table definition file \

Background

[Any helpful contextual notes or links to artifacts/evidence, if needed]

Security Considerations (required)

[Any security concerns that might be implicated in the change. "None" is OK, just be explicit here!]

Sketch

[Notes or a checklist reflecting our understanding of the selected approach]

[rshewitt]

needs to occur before #4744

[rshewitt]

columns are nullable by default (source). just wanted to share

[rshewitt]

a conclusion that we reached in our stay-after is to drop sqlite and look into scaling another instance of postgres. one for the flask app and another one for db integration tests. we also discussed moving the flask app out of the compose file and into the makefile