Streamlining the input parsing and creation of Moorings:

- Project.loadDesign: Work in progress adapting the YAML loading
  to be more simple and bottom-up, parsing all contents in reverse
  hierarchical order.
- - Removed some error checks that would become redundant.
- - Implemented simpler reading of mooring config info into design
    dictionaries, stored in Project.mooring_configs.

- Project.addMooring: modified to use more integrated approach that
  supports look for an entry in Project.mooring_configs.
- - To do: see if naming convention can be fully implemented in here.

- Helpers:
- - getMoorings (duplicate name of Platform method) replaced
    with loadMooringConfig, edited version with some streamlining
    and no explicit Project dependency.
- - Added ConnectorProps, similar to MooringProps for connectors.

- Edited some test YAMLs to have clump_weight 20 or 80 as needed.

NOTE: As these changes are implemented, YAMLs that have leftover unused
entries with missing references will raise errors more reliably.

Author: mattEhall

examples/OntologySample200m.yaml

@@ -329,10 +329,6 @@ mooring_connector_types:
         m  : 140    # [kg]  component mass
         v : 0.13   # [m^3] component volumetric displacement
 
-    clump_weight_20:
-        m   : 20000  # [kg]
-        v :  0.8   # [m^3]
-        
     clump_weight_80:
         m   : 80000  # [kg]
         v :  0.0   # [m^3]

examples/OntologySample600m_shared.yaml

@@ -492,6 +492,10 @@ mooring_connector_types:
         m   : 140    # [kg]  component mass
         v   : 0.13   # [m^3] component volumetric displacement
 
+    clump_weight_20:
+        m   : 20000  # [kg]
+        v :  0.8   # [m^3]
+        
     clump_weight_80:
         m   : 80000  # [kg]
         v   :  0.0   # [m^3]