[3pt] GVAL rio write_crs warning

[RobHanna-NOAA]

Soon PR 1217 will be merged which has a number of upgrades, which include OpenJDK and a bunch of python packages. One of the packages upgraded is GVAL, which now goes up to 0.2.7.

When FIM runs indirectly calls GVAL, a large number of new warnings are being issued. It is filling our screen output and masking possible true issues.

/usr/local/lib/python3.10/dist-packages/gval/comparison/agreement.py:134: FutureWarning: It is recommended to use 'rio.write_crs()' instead. 'rio.set_crs()' will likelybe removed in a future release.
agreement_map.rio.set_crs(crs, inplace=True)

Granted, It is assume the warning is coming from GVAL,. but this needs to be confirmed.

It is strongly encourage not to add code to suppress warnings, but it is encouraged to address them to avoid future surprises.

[RobHanna-NOAA]

Greg fixed and released gval=="0.2.7.post1" but in testing, it does not appear to fix the problem. This is a low priority and can be re-assessed after the docker updates via 1217 are merged.