* remove wav_grdout routine, now moved into wav_history_mod

* remove more cap stuff from w3iorsmd. only ww3 native filenaming
is possible w/ binary restarts
* remove ifdef w3_ascii from w3wavemd, since the ascii commit is not
yet present in mesh cap branch
* clean up config variable logic for filenaming

* nrqrs can be non-zero if also using the restart from binary
option

* flpart needs to be set for either historync or not

* move restart and history nc blocks outside of ww3 time testing
block.
* add log print messages for reading and writing restarts

* get logging working correctly for ufs
* fix noclobber variable and file name in wav_history
* clarify some comments

* make binary history files match when restartnc=true
* rework wav_restart_mod, which originally was designed to be able
to read and write restarts for testing purposes from inside wav_comp_nuopc.

* verboselog is true by default, but can be set false by config
* the header text for ww3 logging as it steps through time is now
turned off in w3init and placed into the mesh cap. this allows the
mesh cap to order the logging correctly

* move block where addrstflds was set to before call to w3init
since restarts are read in w3init
* ensure that if nml file lacks a specification of extra fields,
the default value of "unset" will not be returned as a field name

* only ice is added for now
* tab cleanup in w3grid

* need to send explicit array bounds for ice array since
it is 0:nsea
* all baselines b4b against f9531d0

* intialize floutg and floutg2 which are can be unintialized when
waves are in slow loop and historync is true

* local arrays dimension nx or greater are locally allocated
* deallocations added, even though not required for user clarity

…o feature/pio4ww3

* global_input and _output can be allocatable

* tested by using nco to alter the nth,nk values in a restart
file. The model correctly aborted after finding nth did not
match the expected value

* delay the deallocation of gindex arrays until after the diagnose_mesh
routine is called. This only impacts cases where dbug_flag>5, compiled
with gnu+debug