Maintain and update data atmosphere tests to support applications

[NickSzapiro-NOAA]

Current ufs-weather-model regression tests involve some older data atmosphere tests (e.g., with CFSR forcing) and other possibly stale ones.

Recently, @jkbk2004 helped check-in with the NG-GODAS side that it's ok to re-focus those efforts on RTOFS development.

Land, HAFS, and other teams may also use these configurations, at least in development. I would like to check-in with folks on whether the current tests are relevant/useful, updates are planned, or new tests should be set up
@dpsarmie @barlage @uturuncoglu @BinLiu-NOAA @sanAkel @yangfanglin

In particular,

• Are the datm_cdeps_lnd* relevant? Maybe your workflows involve ATM with sfcsub instead
• HAFS had a hafs_regional_datm_cdeps using HYCOM, but I don't see a replacement

[sanAkel]

@NickSzapiro-NOAA Thanks for starting this discussion. The following 2 items always come to my mind:

1. For coupled model development, we always rely on improving individual components- therefore, datm_xx; xx = lnd, ocn, etc, is (always) relevant!
2. Periodical update and clean up of the infrastructure (files, scripts) is also important.

[JessicaMeixner-NOAA]

A data component used with wave modeling (inputs of atmophere and other inputs), would be helpful for RWPS so we can take advantage of some of the features that are only available in the NUOPC cap.