Add the Stokes Forces Implementation for the Surface Bands wave coupling method

[alperaltuntas]

This PR adds the Stokes Forces implementation by @breichl and some additional refactoring and bug fixes.

The summary of Stokes Forces changes (@breichl):

• Introduction of the stokes forces based on the 3d Stokes drift profile. The 3d Stokes drift profile is obtained via the partitioned Stokes drift components exported from WW3. The added forces are the duS/dt term, the updated pressure gradient force, and the the vorticity modifications. For the duS/dt term, the increment tendency is computed whenever the Stokes drift is updated. This term is applied on the dynamics time step. The pressure gradient force is being calculated outside of the model's pressure solver, and the Stokes-shear terms at cell centers and then integrating and taking gradients to estimate a pressure gradient tendency anomaly. This isn't the correct way of incorporating the pressure gradient force, so will be corrected soon.

The summary of refactorings and bugfixes (@alperaltuntas) :

• Add the ability to import fields with ungridded dimensions in NUOPC cap.
• Add a more flexible and concise way of exporting partitioned stokes drift components from WW3. This is based on utilizing the NUOPC ungridded dims feature. The new way of exporting these fields is encapsulated with if (cesm_coupled) checks. However, when the anticipated unification of EMC and NCAR WW3 nuopc caps is accomplished, the old way of exporting the partitioned stokes drift components may be removed to get rid of duplicate code.
• Fixed the exact restart test failures by adding the 3d stokes drift field to the restart file. To do so, minor refactoring is done in wave_interface module and calling driver modules.
• other bugfixes: remove unnecessary ampersands from variable declarations. enclose stokes vorticity diag computations with Stokes_VF conditional. Do not call get_Langmuir_Number if lamult is already provided via ww3. Fix openmp test by adding Stokes_VT to shr clause.

[codecov-commenter]

Codecov Report

Merging #205 (4f592f2) into dev/ncar (3d86e71) will decrease coverage by 0.05%. The diff coverage is 12.50%.

@@             Coverage Diff              @@
##           dev/ncar     #205      +/-   ##
============================================
- Coverage     29.06%   29.01%   -0.06%     
============================================
  Files           237      237              
  Lines         71635    71842     +207     
============================================
+ Hits          20822    20845      +23     
- Misses        50813    50997     +184     

Impacted Files	Coverage Δ
src/parameterizations/vertical/MOM_CVMix_KPP.F90	1.00% <0.00%> (ø)
src/user/MOM_wave_interface.F90	1.50% <5.19%> (+0.66%)	:arrow_up:
src/core/MOM_dynamics_split_RK2.F90	59.46% <16.66%> (-1.62%)	:arrow_down:
src/core/MOM_forcing_type.F90	47.25% <25.00%> (+0.02%)	:arrow_up:
src/core/MOM.F90	58.88% <27.27%> (-0.13%)	:arrow_down:
src/core/MOM_CoriolisAdv.F90	38.30% <28.26%> (-0.97%)	:arrow_down:
config_src/drivers/solo_driver/MOM_driver.F90	68.20% <50.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more Δ = absolute <relative> (impact), ø = not affected, ? = missing data Powered by Codecov. Last update 3d86e71...4f592f2. Read the comment docs.

[alperaltuntas]

@gustavo-marques this is ready to be tested and merged.

[gustavo-marques]

@alperaltuntas, I have verified that this PR does not change answers for the MOM6-examples test suit w.r.t. the latest main (https://github.com/NCAR/MOM6/commit/9cb93044ef06a929171b5bd326a7c5c06aa72316). Were you able to run the CESM tests?

[alperaltuntas]

@gustavo-marques Yes, the aux_mom test suite passes.