ED: update blade file parser to allow arbitrary column locations

[andrew-platt]

Ready to merge

Feature or improvement description
Some of the IEA turbine models include the PitchAxis column as well as additional columns that ElastoDyn does not use. Simply deleting the PitchAxis column from the table is insufficient as the parsing will fail due to more than 5 colunns still remaining. This PR generalizes the reading of the blade properties table to select the 5 columns needed based on the names in the header, and ignore any others. Columns also don't need to be in order anymore.

Related issue, if one exists
None. Reported internally.

Impacted areas of the software
ElastoDyn blade file parsing only.

Generative AI usage
None

Test results, if applicable
No test results change

[Copilot]

Pull request overview

This PR updates ElastoDyn’s blade input file parsing so the distributed blade properties table can contain additional columns (e.g., PitchAxis) and arbitrary column ordering, by selecting the required 5 columns based on header names and ignoring the rest.

Changes:

• Add header parsing (GetBldTbleCols) to locate required table columns by name.
• Update table reading to parse an arbitrary number of numeric columns per row and map required fields via the discovered column indices.
• Remove the previous hard failure when extra columns (like PitchAxis) are present.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.