feat: track gloss history

[tycebrown]

What has changed

• Created the GlossHistory table as described in issue #340
• Whenever a user updates a gloss, a row is added to this table
• Whenever the user imports glosses from the old site, a column (🤣) row is created for each gloss imported.

  Connected Issues

  closes #340

QA Steps

1. Reset the database to use the updated schema (nx run db:prisma migrate reset)
2. Query the contents of the GlossHistory table. Confirm that it is empty.
3. Change the gloss text for a word. Confirm that a new column is added to the GlossHistory table with the updated gloss text.
4. Then, change the gloss approval state without changing the gloss text. Confirm that a new column in GlossHistory is created with the updated approval state and null for the gloss text.

Post-Deployment

• [ ] Nothing required

[Pertempto]

I plan to review this in the morning

[Pertempto]

Lol

Whenever a user updates a gloss, a column is added to this table

I think you have a mistake there 😆

that would be QUITE the implementation

[Pertempto]

@arrocke are prisma migrations something that should be included in the Post Deployment section, or are they ran automatically?

[arrocke]

@arrocke are prisma migrations something that should be included in the Post Deployment section, or are they ran automatically?

These are run automatically on merging

[Pertempto]

If you think it's worth the check I can do all the setup on my local env and test it tomorrow.

[arrocke]

@Pertempto @tycebrown I will take a look at this tomorrow