Move names and aliases to their own table

[brendanreardon]

Task Description
Currently, names are included for each record in the dereferenced database, as well as aliases. We will create a separate table called names that both the name and aliases fields will point to for all records in the database.

Objective and requirements
Reduce data duplication by moving names and aliases to their own JSON file.

Implementation Steps
Most tables within the dereferenced version of the database use names and/or aliases for fields. An approach to resolve this Issue may be:

1. Generate the set of all current names and aliases amongst tables and place them in a new file, names.json.
2. Iterate through each table, replacing the name or alias with the referenced id from the names table.
3. Dereference the names and aliases for each table, and check that the names and aliases were reconstructed as anticipated.
4. Update the database schema schematic to reflect this change.

There are some extension fields that may be relevant for this Issue. Specifically, company, brand_name_drug, and brand_name_generic from the Documents schema.

Dependencies
No specific dependencies.

Additional Context
The README for the in development version of the database that follows GKS specifications will be useful to linking out to appropriate documentation from GA4GH, and providing a visual representation of the database.

Estimated Time
(Optional) This is likely a full day of programming work to resolve this Issue.

Priority
(Optional) Low. This is a nice to have.