Feature request: MD out file

[RBergua]

Is your feature request related to a problem? Please describe.
It seems that when MoorDyn module is included in an OpenFAST simulation, the results are always written down in the OpenFAST output file as well as the MoorDyn output file. See below for reference (example running OpenFAST dev):

This duplication of the results may slow down the computational since both output files need to be written at every time step. Moreover, having two output files takes disk space.

Describe the solution you'd like
Other modules (e.g., SubDyn) have a flag that allows the user specify where the results should be written down. See below for reference:

[RyanDavies19]

This will be addressed in #2597