Add debug information to fglob function

[metdyn]

Types of change(s)

• 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

• Tested this change with a run of GEOSgcm
• Ran the Unit Tests (make tests)

Description

Added _FAIL to sub. fglob, if pathlen exceeds upper bound of filename length (ESMF_MAXSTR).
I find this could be a potential problem and we need the debug information.

Related Issue

[mathomp4]

Hmm. If we are using ESMF_MAXSTR (which is 256) anywhere for a path, you might want to find those and change them to ESMF_MAXPATHLEN (which is 1024).

@bena-nasa, @atrayano, and myself can regale you with fun that has happened in the past with paths longer than 256!