Fix WISDEM API connections #114
Description
In resolving #113, I identified some inconsistencies between case setups for the BOS and various WISDEM-derived components. Diff between api/default_systems cases with/without collections and between the default systems for onshore/monopile/floating to ensure changes are right.
The BOS promotions should trap total_capex from promotion so that they're not interpreted as being turbine-inclusive capex but always are subordinate to the BOS module while named such. The promotions more generally need to consistently treat turbine count, rating, description, etc., and currently do not