Add ALM reg tests

[marchdf]

Summary

Add an ALM openfast reg tests. It's time. As much as we've been resisting this... It's critical enough and I recently broke something (#1385) that would have been caught if we had a reg test.

Pull request type

Please check the type of change introduced:

• Bugfix
• Feature
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no api changes)
• Build related changes
• Documentation content changes
• Other (please describe):

Checklist

The following is included:

• new unit-test(s)
• new regression test(s)
• documentation for new capability

This PR was tested by running:

• the unit tests
  • on GPU
  • on CPU
• the regression tests
  • on GPU
  • on CPU

[marchdf]

So far I have this. Red = T0, first run, green = T1, first run, blue = T0, restart run, orange = T1, restart run. They all do the same thing, which is expected. And blue and orange start later (since they are a restart)

turbines.pdf

[marchdf]

And with this restart case I can confirm the breakage I saw in #1385 and that breakage is not in 3.2.0.

[lawrenceccheung]

Thanks @marchdf, this is great and something that has been sorely needed.

I'm adding in a note that the input files were generated with the notebook https://gist.github.com/lawrenceccheung/a775e8eb5162e906da2a75ce67169139, in case we want to generate other reg test type problems in the future.

Also, we should adopt a similar process of downloading the NREL5MW files from OpenFAST/r-test for the benchmark problems. Or least, noting which commit they were downloaded from and documenting which changes to the openfast model were necessary for the benchmark problems to run. I know it's for a separate problem, but we should be handling them consistently (Tagging @ndevelder on this).

Lawrence