Refactor conditions.category migration

[robertandremitchell]

Per this PR: #88

We have some ongoing work around refactoring all of our migration work. For now, we are adding that via a CSV provided by APHL in a migration.

However, that adds a volume to the migration step that we would prefer not to have. Two potential paths forward:

1. Convert the CSV dynamically to a series of INSERT statements that then do the UPDATE to the conditions table to avoid having a volume. This might involve writing a script to make these dynamic INSERT statements with each new publication of the eRSD to avoid as much manual editing as possible.
2. (More ideal) Work with contacts at APHL to get category represented in the eRSD data so that it can be built out as a column at the same time during database creation.

[linear]

QUE-43 Refactor conditions.category migration

[robertandremitchell]

fixed as part of work on other ticket.