Replace FluidLoop and FluidLoopDesignAndControl with linked components

[JasonGlazer]

Since loops are not part of the architecture of all BEM software, replace that approach with one that links components together and attaches the controls that are currently in FluidLoop and FluidLoopDesignAndControl to those components. The components are:

• HeatingSystem
• CoolingSystem
• Terminal
• Boiler
• Chiller
• HeatRejection
• Pump
• ExternalFluidSource
• ServiceWaterHeatingEquipment
• MiscellaneousEquipment

Also, make the type of "loop" based on its components, so instead of saying something is a hot water loop, it is a hot water loop based on the presence of a boiler.

Items in the current FluidLoop and FluidLoopDesignAndControl data groups that would have to be relocated:

• type (heating/cooling/heating and cooling/condenser)
• pump_power_per_flow_rate
• design_supply_temperature
• design_return_temperature
• is_sized_using_coincident_load
• minimum_flow_fraction
• operation (continuous/intermittent/scheduled)
• operation_schedule
• flow_control (fixed/variable flow)
• temperature_reset_type (no reset/outsider air reset/load reset)
• outdoor_high_for_loop_supply_reset_temperature
• outdoor_low_for_loop_supply_reset_temperature
• loop_supply_temperature_at_outdoor_low
• loop_supply_temperature_at_outdoor_high
• loop_supply_temperature_at_low_load
• has_integrated_waterside_economizer

It might make sense to have a FluidTemperatureControl data group that would encapsulate many of these.

Note that SPC 205 is working on a topology task that might be related for connecting the components.

@TimMcDowell and @nealkruis and @buckles1 please feel free to add more suggestions.

[JasonGlazer]

This was discussed during the October 11, 2024 schema working group call. We decided that the next step was to mock up the changes on a separate branch to see how they would work. This would follow the approach being used in Std 205 and Std 223 which (I believe) are both still being developed.