Clean up input & configuration files for FLORIS

[cfrontin]

the originial implementation would uses three configuration files on the way to a FLORIS solve:

• windard/examples/FLORIS_power_comp/data/turbine_spec_IEA-3p4-130-RWT.yaml
  • my centralized configuration file to centralize input data across multiple tools
• windard/examples/FLORIS_power_comp/data/FLORIS.yaml
  • FLORIS configuration data
  • also carries farm layout information, which is overwritten
• windard/examples/FLORIS_power_comp/data/FLORIS_turbine_library/IEA-3p4-130-RWT.yaml
  • FLORIS turbine input, generated automatically by the run

This is messy, and should be improved, even before (and towards) moving on to full windIO integration.

[cfrontin]

Driven by windio as of #120