Updates for windio 2.1

[dzalkind]

Purpose

Conform to latest windio schema, v2.1

Type of change

What types of change is it?
Select the appropriate type(s) that describe this PR

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (non-backwards-compatible fix or feature)
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no API changes)
• Documentation update
• Maintenance update
• Other (please describe)

Testing

Explain the steps needed to test the new code to verify that it does indeed address the issue and produce the expected behavior.

Checklist

Put an x in the boxes that apply.

• I have run existing tests which pass locally with my changes
• I have added new tests or examples that prove my fix is effective or that my feature works
• I have added necessary documentation

[dzalkind]

I am not such of fan of this. I made these tables in ROSCO, which uses some defined cut-in wind speed, sometimes coming from wisdem/weis, so it's a bit circular.

I would vote for a cut-in/cut-out wind speed explicitly defined somewhere. I prototyped an addition to the control geometry schema in WISDEM if we want it there, but I also think it could go under assembly. Thoughts?