Found and fixed a bug in the glob() routine

It turns out that when I moved Tim's glob() routine into the
Filerator.chpl module, I changed a c_int return type of
chpl_glob_num() to a size_t to better reflect the C interface.
However, in doing so, I also introduced an error because we iterated
over the range:

     0..chpl_glob_num(...)-1

which, for a glob() call with no matches, resulted in:

     0..0:uint(64)-1

or:

     0..max(uint(64))

which is a range that we generate overflow warnings for.  In Tim's
original code, this just resulted in 0..-1 which wasn't an issue.

This commit fixes the bug by checking against '0' before entering the
loop over the range.  It also files a few test cases that exercised
the bug and updates the output of the globberator.good file to
reflect the new tests.

(cherry picked from commit a5d04fef8e38fcf1000563ad4df3f1dca930c8da)
Merge pull request #582 from bradcray/promote-glob-fix-to-1.10

Found and fixed a bug in the glob() routine

Promoting a5d04fef8e38fcf1000563ad4df3f1dca930c8da to the release branch