Add file readers and writers into automated testing

[andrew-platt]

PR #2188 added input file readers and writers from WEIS into the main OpenFAST repository. These readers and writers should be exercised as part of the automated testing in GH actions.

One approach would be to add an option to cmake (CTEST_ENABLE_READER_WRITER=On or similar) that would run all input files for glue code regression tests from OpenFAST through the respective readers and writers. This would allow running testing locally without the readers/writers in the loop while doing development work (new modules, or troubleshoot). A few things to consider:

• Should we add an optional argument in CTestList.cmake to only run the reader/writer testing on specific tests?
• Would filenames in a given test need to be standardized (i.e. ElastoDyn.dat instead of NRELOffshrBsline5MW_OC4DeepCwindSemi_ElastoDyn.dat)?

@mayankchetan, @andrew-platt