Fixes from integration with SRW's make_orog

[christinaholtNOAA]

Synopsis

A set of changes to the drivers run as part of SRW's make_orog task.

• Run commands seemed not to work as expected, so changed them to use config files.
• More information was needed in the UW YAML in a couple of instances.

Also ordered the tests in each of the drivers.

Type

• Bug fix (corrects a known issue)
• Code maintenance (refactoring, etc. without behavior change)
• Documentation
• Enhancement (adds new functionality)
• Tooling (CI, code-quality, packaging, revision-control, etc.)

Impact

• This is a breaking change (changes existing functionality)
• This is a non-breaking change (existing functionality continues to work as expected)

Checklist

• I have added myself and any co-authors to the PR's Assignees list.
• I have reviewed the documentation and have made any updates necessitated by this change.

[maddenp-noaa]

Whatever you decide to do w.r.t. the hardcoded orog filename(s) will be fine. On principle, and just repeating what I already argued, I think that values that are not configurable should not appear in configuration, but should be derived from actual configurable values. That might not be practically attainable immediately.

[WeirAE]

Whew, I think I got through everything - great fixes!