updates for geostationary output part 1

[bena-nasa]

@amdasilva requested that History be able to output geostationary data. This can be described via rectilinear grid with some missing points. We can trivially extend the XY grid factory (which was as generic factory for arbitrary creation of rectilinear grids from a file) for this.
For part 1 this PR will assume the user has converted them to a form that the XY grid factory understands
I tested by obtaining the coordintes (lats and Lons on the sphere) for GOES-16 here
https://www.star.nesdis.noaa.gov/atmospheric-composition-training/satellite_data_goes_imager_projection.php
and converting to the form needed by XY factory (dimensions must be Xdim and Ydim, and will have lons(Xdim,Ydim), lats(Xdim,Ydim)).

The new features are thus

1. The xy grid factory now tests if any points are missing, if so it adds a mask to the ESMF grid and masks at the appropriate points
2. A few new MAPL constants were defined to be the masking parameters
3. The MAPL wrapper to ESMF regridders was updated so that it checks if the destination grid has a mask. If so it adds the dstMaskValues argument to the restore. For now limited to linear regrid, could be extended to other methods. I also now set the value of the destination field to MAPL_UNDEF rather than 0 before the ESMF regrid method is called on the destination field to be regridded. In this way any points that are masked out are MAPL_UNDEF, rather than 0, probably for plotting.

From here @metdyn can extend the grid factory to support the input format @amdasilva showed us if required that requires converting from raw satellite angle inputs via some geometry to lats and Lons on the sphere which is what we really need.

Finally here's a picture so show that this does work, the heights regridded to goes-16 view using the coordinates I obtained from the link earlier in the PR

Description

Related Issue

Motivation and Context

How Has This Been Tested?

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Trivial change (affects only documentation or cleanup)

Checklist:

• I have tested this change with a run of GEOSgcm (if non-trivial)
• I have added one of the required labels (0 diff, 0 diff trivial, 0 diff structural, non 0-diff)
• I have updated the CHANGELOG.md accordingly following the style of Keep a Changelog

[metdyn]

Thank you, @bena-nasa, for your work! The code is working with the lambert_grid on the Mac and I am proceeding based on your PR.

[tclune]

Very nice implementation and description.

A couple of small "suggested changes", and a bigger "something to think about".