Enhancing tests for design module's total cost

[nRiccobo]

Updated several design tests to include some kind of "test_total_cost". A simple test like this should capture a snapshot of the design module's total cost for given a base case. Further, this will aid in tracking if any logic, default costs, or cost algorithms change between additions.

Additionally, I addressed some potential if-statements matching issues in electrical_design and mooring_system_design that @rafmudaf noticed in #171.

[rafmudaf]

Thanks @nRiccobo, nicely done.

Just a comment - using the form "key" in self.config["key"].lower() instead of self.config["key"].lower() == "key" means that ORBIT will support inputs that have the right parameter somewhere within the string such as "mooring_system_design": {"mooring_type": ["SemiTautttt"]}. That kind of flexibility can be really nice, but it's not the usual so I just wanted to point it out in case it wasn't intentional. You'll also have to be careful not to add a valid config value that appends something to an existing value like "HVDC_aluminum" etc for the cable.

Also, you could consider making all the inputs lower case in load_config and then use lower case in all the if-statements, and this would remove .lower() everywhere else. It's probably a painful amount of work to catch this everywhere, though.

Just my two cents. Thanks for addressing my other comment @nRiccobo!

[RHammond2]

Thanks for getting these additional checks in place!

I think you opened up a small can of worms with some of input handling methods, otherwise the only thing I'd add is a total design cost for the default fixed and floating scenarios to ensure all the costs are double checked.

[RHammond2]

I see how this is now annoying because there are many forms of standardization this could take.

[nRiccobo]

Yeah... Never a one size fits all, heh.

[RHammond2]

We could probably think a bit more on the capitalization of SemiTaut, TLP, etc., but I think it's good to go as-is.