[rrfs-nco] Check dbn_alerted filenames

[JamesPolly-NCO]

db_net logs appear to have some funny file names:
/lfs/h1/ops/para/com/rrfs/v1.0/firewx.20260310/dbnlogs/rrfs_firewx_post_f000_00.2026031000.dbnlog

[02:35:28] MODEL rrfs_firewx_post_f000_00 /lfs/h1/ops/para/com/rrfs/v1.0/firewx.20260310/00//lfs/f1/ops/para/tmp/rrfs_firewx_post_f000_00.100083603.dbqs01/rrfs.t00z.natlev.1p5km.f000.firewx.grib2

We need to run our parallel with export NODBNFCHK=YES set in version/run.ver to try to catch these.

[WeiWei-NCO]

It's missing a subtype, and filename/path is messed up.

I don't think we ever set export NODBNFCHK=YES manually. I will double check, but we probably don't want to set it for rrfs.

Edit:
It should fail for non-existing file, but it only printed WARNING because it's missing a subtype. If we have the subtype, it would fail without export NODBNFCHK=YES , and we want it to fail.

if [ ! -s $4 ]; then
  if [ -f $4 ]; then
     >&2 echo "WARNING: $4 is empty (it has a size of zero bytes)"
  else
     if [ "${NODBNFCHK^^}" == "YES" ]; then
        >&2 echo "WARNING: $4 is not exist"
     else
        err_exit "Fake dbn_alert could not find $4"
     fi
  fi
fi