Update MOM6: routine maintenance-2022-11-10

[sanAkel]

This PR updates GEOS- MOM6 CMakeLists.txt to be consistent with mom-ocean/MOM6#1586 once that is merged.

This PR changes answers because of community agreed upon change in MOM6 defaults, impacts only the MOM6 based GEOS coupled model.

Steps to follow:

• @sanAkel undraft this PR when @marshallward merges GFDL to main 2022-10-27 mom-ocean/MOM6#1586
• @mathomp4 and/or @tclune please review
• @mathomp4 please use your powers to merge and update our MOM6 fork.

Thank you!

[mathomp4]

@sanAkel It looks like @marshallward did the merge. If all is good for you, I can update the fork.

[sanAkel]

@sanAkel It looks like @marshallward did the merge. If all is good for you, I can update the fork.

@mathomp4 Please go ahead with the update. However, until the @GEOS-ESM/cmake-team approves, the CMakeLists.txt will be inconsistent with the updated source code.

If possible, first review the PR and then merge. Thanks!

[mathomp4]

@sanAkel It looks like @marshallward did the merge. If all is good for you, I can update the fork.

@mathomp4 Please go ahead with the update. However, until the @GEOS-ESM/cmake-team approves, the CMakeLists.txt will be inconsistent with the updated source code.

If possible, first review the PR and then merge. Thanks!

@sanAkel I did both. Obviously, you'll need/want to make a release of MOM6 so you eventually component-ize this.

[sanAkel]

Great! Thanks!!

Looks like I can't merge, would you please do it ?

Or should I first make a release of MOM6? Done!

[mathomp4]

As this will never pass CI until a new version of MOM6 is in the components.yaml of GEOSgcm, for now I'll force merge. Then @sanAkel can merge to main, make a new version of GEOS_OceanGridComp, and can make a PR to GEOSgcm for @sdrabenh