Multiple Rotor Implementation into RAFT for CT-Opt work

[shousner]

• Added two new test input files (test.yaml and test2.yaml) that work with this new multiple rotor feature (the old design input yamls still work).
• The turbine dictionary can now be read in similar to how properties of members are read in: they can either be scalar or arrays, and the helper function getFromDict() will create the proper size of RAFT attributes based on the specified number of rotors in the system (default=1)
• Dictionaries within the turbine dictionary, like 'blade' and 'tower' can have either a list of dictionaries for different objects, or keep the singular dictionary. There is an if statement in the code that will handle the difference between dicts and lists
• Most of the rotor-related variables in the code now have an extra dimension to their matrices