Capacity factors added to Components

[GabrielSoto-INL]

---

Pull Request Description

What issue does this change request address?

121

What are the significant changes in functionality due to this change request?

New input node for Components allows user to apply capacity factors to the nameplate capacity. <capacity_factor> is applied parallel to the <capacity> node. Currently only allows Synthetic History (ARMA) input to be applied as a per-unit-time capacity factor.

Adding new tests based off the initial wind workshop case (simplified with Sine ARMA). Results are tested against the previous way that the wind workshop case was implemented: <capacity> took a Synthetic history valued param and the <multiplier> would contain the intended nameplate capacity. A copy of that script also included in test directory.

---

For Change Control Board: Change Request Review

The following review must be completed by an authorized member of the Change Control Board.

• [x] 1. Review all computer code.
• [x] 2. If any changes occur to the input syntax, there must be an accompanying change to the user manual and xsd schema. If the input syntax change deprecates existing input files, a conversion script needs to be added (see Conversion Scripts).
• [x] 3. Make sure the Python code and commenting standards are respected (camelBack, etc.) - See on the wiki for details.
• [x] 4. Automated Tests should pass.
• [x] 5. If significant functionality is added, there must be tests added to check this. Tests should cover all possible options. Multiple short tests are preferred over one large tes.
• [x] 6. If the change modifies or adds a requirement or a requirement based test case, the Change Control Board's Chair or designee also needs to approve the change. The requirements and the requirements test shall be in sync.
• [x] 7. The merge request must reference an issue. If the issue is closed, the issue close checklist shall be done.
• [x] 8. If an analytic test is changed/added, the the analytic documentation must be updated/added.
• [x] 9. If any test used as a basis for documentation examples have been changed, the associated documentation must be reviewed and assured the text matches the example.

[GabrielSoto-INL]

PR is now ready for review