fsurdat file needed for NEON MOAB site

[samsrabin]

I didn't want to open a whole new issue for this BUT...
In #2500 this test changed from FAIL (expected) to PEND in the SHAREDLIB_BUILD phase
SMS_Ld10_D_Mmpi-serial.CLM_USRDAT.I1PtClm60Bgc.derecho_gnu.clm-NEON-MOAB--clm-PRISM
with this error CLMBuildNamelist::add_default() : No default value found for fsurdat.

Same on izumi:
SMS_Ld10_D_Mmpi-serial.CLM_USRDAT.I1PtClm60Bgc.izumi_nag.clm-NEON-MOAB--clm-PRISM

Originally posted by @slevis-lmwg in #2310 (comment)

---

I'm elevating this to its own issue because now the cs.status output is confusing, and the expected failure isn't detected.

[samsrabin]

Note that the cs.status output will make more sense—i.e., SETUP will be marked as FAIL—once we bring in cime6.1.27 or later; see ESMCI/cime#4681.

[slevis-lmwg]

The file already exists here (78pft)
/glade/campaign/cesm/cesmdata/inputdata/lnd/clm2/surfdata_esmf/NEON/ctsm5.3.0/surfdata_1x1_NEON_MOAB_hist_2000_78pfts_c240912.nc
and here (16pft)
.../16PFT_mixed/surfdata_1x1_NEON_MOAB_hist_2000_16pfts_c240912.nc

[samsrabin]

So I guess something just needs to be changed in the XML for the test to pick that up?

[slevis-lmwg]

@samsrabin this sounds simple, although @olyson and I looked at this for a few minutes this morning and found:

1. The fsurdat setting seems correct in namelist_defaults_ctsm.xml
2. Other neon tests work suggesting that this test does something different that causes it to break...

[slevis-lmwg]

Additional info. This test works:
SMS_Ld10_D_Mmpi-serial.CLM_USRDAT.I1PtClm60Bgc.derecho_gnu.clm-NEON-MOAB

[samsrabin]

Ah, so it seems like the addition of the PRISM testmod is the issue.