Make new Database Tables for TrueFile codes

[BryceStevenWilley]

Few steps before we actually add the new tables:

1. Abstract out the idea of codes into best interfaces we can get. As of Moving classes and packages around #397, CodeDatabaseAPI is the current place for vendor-independent codes, but most of our implementation depend on CodeDatabase (should be renamed to TylerCodeDatabase). Should make sure that all the APIs (including the rest endpoints, if possible) are generic to what specific tables are there.
2. Really a subpoint of the above, but whether a certain code exists or not for a jurisdiction (not just "empty"). IMO it could either be adding Optionals around all return types for the CodeDatabase, or just nulls / no-ops, and a "get available" method that returns what endpoints actually do something in this impl.
3. NameAndCode reused as much as it can, and only get the specific tyler vs TrueFile Implementations in those specific classes. Again, after Moving classes and packages around #397, CodeDatabaseAPI has the methods for getting just NameAndCode, and it should be used internally and on the python side as much as it can.