Feature DEPHY v1

[dustinswales]

This PR adds the ability to use DEPHY v1 forcing files with the SCM.

The changes are isolated to the scm input/output/util modules to accommodate the new format (see DEPHY v1 doc)

• From DEPHY v0(?) -> v1 there was a change in the format to remove the spatial indexing. For example, 2D data format changed from [x, y, z, time] -> [z,time].
• Variable name changes.
• New input argument (char) for the "check" subroutine. Calls to check were modified to print this descriptor when there is an error. (There were variable name changes from DEPHY v0 -> v1, and knowing what was failing was impossible w/o this added input to check)

There is a new case configuration file and CI test to exercise the SCM's compatibility with the DEPHY repository, ci_run_scm_DEPHY.yml. (If they change their format, yet again, this test will break. At which time we can decide to either update the SCM to use the latest DEPHY format or just use the last working hash in the DEPHY repository.)

This replaces part of #364

[dustinswales]

@grantfirl All tests pass. No changes to baselines.

[dustinswales]

Looks good, @dustinswales . Just a few questions.

@grantfirl Thanks for your review.

There are some documentation changes that I need to add. I don't have a latex editor on my work machine to update main.pdf, and these changes are on my home computer. So I will update the PDF later. Question. Do we update the date on the Users Doc?

[grantfirl]

Looks good, @dustinswales . Just a few questions.

@grantfirl Thanks for your review.

There are some documentation changes that I need to add. I don't have a latex editor on my work machine to update main.pdf, and these changes are on my home computer. So I will update the PDF later. Question. Do we update the date on the Users Doc?

We've only updated the date for releases in the past, but it's also fine if you'd rather do that now too.