2.38.00: Backend Schema Updates

This update represents a major re-factor of C.Scale's internal schemas and how they're managed. These changes will not be visible on any of the exposed endpoints. Additionally, this change includes a minor update to the stacked building_form
 to better handle instances where the list of levels is not sequential.
Schema Updates
Objects shared by more than one request schemas are now all pulled from a single source of truth. Default values previously stored in the schema itself are now injected via functions.
These changes pay down a significant amount of the technical debt we had accrued in keeping our schemas backwards-compatible. This will allow us to develop future features faster. Additionally, this clears roadblocks for the near-term development of "smarter" defaults dependent on building type, building form, relevant standards, and other characteristics of the model. 
This change has no effect on the API's use or functionality. 
Hotfix for Stacked Building Form
The stacked building_form
 object was originally written to deal with non-sequential levels correctly (e.g. if the passed levels are 0,1,3,5,6
). But today we learned that the API struggled when the order of the levels in the list did not match the sequence of levels in the building (e.g., 3,5,6,0,1
). Moving forward, we now sort all levels to be sequential before evaluating them. In these cases, we pass message_0018
: The building levels in the request were listed out of order. They have been automatically re-ordered prior to calculation. 