updates from RTs for wave restart name and nml files

[DeniseWorthen]

Description

Two PRs have been merged and the corresponding changes need to be made in the workflow.

1. https://github.com/ufs-community/ufs-weather-model/pull/1692. This changes the name of the WW3 restart file and fixes https://github.com/ufs-community/ufs-weather-model/issues/1590.

This change required in the nems.configure file is to add user_sets_restname = true in the WAV_attributes:: section. The restart file will then be consistent with the restart names produced by ICE and CMEPS. It will also contain an application specific name, eg. ufs.hafs.ww3.r.YYYY-MM-DD-SSSSS or ufs.cpld.ww3.r.YYYY-MM-DD-SSSSS

2. https://github.com/ufs-community/ufs-weather-model/pull/1407. This added use of nml files for the wave model. The template for the file are ww3_shel.nml.IN. Also, the list of point output is now in a separate file ww3_points.list. Both are located in the UFS tests/parm directory. The structure of the nml that needs to be parsed is

   
   &input_nml
   input%forcing%winds      = 'C'
   input%forcing%currents   = '@[WAV_CUR]'
   input%forcing%ice_conc   = '@[WAV_ICE]'
   input%forcing%ice_param1 = '@[WAV_IC1]'
   input%forcing%ice_param5 = '@[WAV_IC5]'
   /

&output_type_nml type%field%list = '@[OUTPARS_WAV]' type%point%file = 'ww3_points.list' /

&output_date_nml date%field%outffile = '1' date%field%stride = '@[DTFLD]' date%point%outffile = '1' date%point%stride = '@[DTPNT]' date%restart2%stride = '@[DT_2_RST]' /

The variables are consistent w/ the variables in the current inp file with the exception of the forcing fields. These are now either ``C`` for coupled or ``F`` for not. The values for ``WAV_ICE1`` and ``WAV_ICE5`` should be ``F`` unless WW3-CICE6 coupling is used (currently not implemented in UFS). 

For the HAFS application, the use of ``outfile=1`` will now create time-stamped files, for example ``20190829.060000.out_grd.ww3`` in place of ``out_grd.ww3``. 

**Requirements**
<!-- If this is a new feature:  -->
<!-- What does the new code need to accomplish? -->
<!-- Does it require an update to version of software (e.g. modules of NCEPLibs, NetCDF, etc., or GFS components e.g. UFS-Weather-Model, GSI, etc., or updates to system tools e.g. python3) -->
<!-- If this is a bugfix: What is the expected behavior? -->

**Acceptance Criteria (Definition of Done)**
<!-- What does it mean for this to be finished? -->

**Dependencies**
Related: #1277

[DeniseWorthen]

@aerorahul