Database migrations for contributor audio and curation

[CharlieMcVicker]

Before anything else, I recommend the rich diff tool for reading the Markdown table changes!

Tracking

This is required to ship these two tickets.
[DP-186] As a contributor, I want the ability to upload audio to DAILP
[DP-200] As a contributor, I want to be able to see user contributed audio

Context

We have three main kinds of users Contributors, Editors, and Readers.

• Contributors should be able to upload their own readings of individual words on the site
• Contributors and Editors should be able to see all other contributor audio
• Editors should be able to select one of the user-contributed audios to be shown to Readers
• Readers should only see curated audio
• Curated audio is either selected by an Editor or ingested via the big migration process from Google Sheets

Related work

I have a frontend PR (#268) going for this stuff, which will eventually include the GQL mutations that touch this stuff. I want to do these DB migrations on their own so that PR doesn't get any bigger.

[GracefulLemming]

I guess the SQL you wrote is somehow disagreeing with our existing code? I can dig into this more at some point if you'd like

[CharlieMcVicker]

@GracefulLemming can we circle back on this? I'm going to rewrite the migrations for multiple surfaced audio segments. Then can we review why this shut down production last time we merged?