Migrate 2017 & 2018 Public Schools data packages & datasets to follow 2019 schema

[bfreeds]

Currently public schools data packages organize sca_bluebook and doe_lcgms datasets as two distinct tables. For the 2019 data update, EDM is combining them into one dataset, which better represent the information (doe_lcgms is really an extension of sca_bluebook to add more detail/schools that aren't in bluebook, but they follow the same schema).

The public_schools data packages need to follow the same schema for all years (2017, 2018, and 2019) - otherwise we will have to add conditional logic on the backend and frontend to allow for a user who is switching between data packages within the public schools analysis to accomodate this difference between data package schemas.

As it is now, lcgms and bluebooks schools are being merged in the frontend model. By addressing this upstream in the backend data model, we can refactor to simplify the Ember public schools analysis model.

For this issue, we need to:

• [x] Manually combine previous bluebook and lcgms datasets in ceqr_data database to align with new schema. doe_lcgms.2017 an dsca_bluebook.2017 should become ceqr_school_buildings.2017, and same for the 2018 tables. #628
• [ ] Update the rails data packages.
  • [x] modify seeds.db #631
  • [ ] run rails db:seed
  • [ ] Need to ensure that existing project successfully migrate to this new schema.
• [ ] Trace where this impacts backend or frontend application logic and update with the expectation of the new ceqr_school_buildings #629
• [ ] Refactor frontend public schools analysis model #630

Related to #484

[trbmcginnis]

Closing this because it'll be covered in #630