v1.14.1 geoips - VERSION RELEASE - CI sync

[mindyls]

Related Issues

required to close #740
required to close

Reviewer Instructions

• Please confirm this PR is set up to merge from v1.14.1-release branch into main branch
• Review "Files changed" tab
• Confirm appropriate testing was completed for these updates (you may perform tests yourself, or review output included from another reviewer/assignee)

Summary

Changes for version 1.14.1, uploaded with
1.14.1 update on repo geoips.
See release note updates in 'Files changed' tab

See #740 for additional repositories included in this update.
See for dev updates included in this update.

Testing Instructions

See #740 for testing instructions.

Output

See #740 for test output.

Post Merge Steps

Once this PR has been merged, v1.14.1
will be tagged/released on the geoips main branch.

[mindyls]

Note RST release note failure is due to header updates to existing RST release notes. These updates will not happen again, and no new RST release notes will ever be checked in, so we should merge with that CI failing. No other actions failed.

[mindyls]

Ready to merge once we have 2 approvals and all conversations are resolved.

The one failing action is release note check - these just have header updates, and we should never have modifications to RST release note files again since we now auto-generate RST release notes. We should merge with this one remaining failing check since these are expected changes to existing RST release notes.

Additionally, CI is now working on other repositories (geoips_clavrx, geoips_plugin_example, geoips_tropics, ryglickicane, etc), though still fails for the fortran-based repos (including recenter_tc since it requires akima).

When this is merged we'll have to update the ruleset to point to main for doc-test.yaml

[evrose54]

ami.tc.WV.geotiff.sh is still failing for me but everything else seems to be working! LGTM.

[jsolbrig]

This is passing for me with one exception.

ami.tc.WV.geotiff.sh is failing. I'm not sure if this is a difference between the data that NRL and CIRA are using or if it is something else. The data range from 0 to 255. There are three pixels that differ by -2, 5, and 1, respectively.

I do not think that this difference is enough to warrant delaying this release any longer.