Legion built without zlib generates uncompressed logs without warning

[elliottslaughter]

If you build Legion with USE_ZLIB=0 or -DLegion_USE_ZLIB=OFF (or the auto-detect fails), Legion will generate Legion Prof binary format logs, but those logs will be uncompressed. Current Legion Prof expects logs to always be compressed and cannot parse them unless you manually gzip the files. This is confusing for users and makes inefficient use of disk space and bandwidth.

Note this has nothing to do with the ASCII log format. These are binary logs, just uncompressed.

There are two things we could do (individually or in combination) to address this:

1. Teach Legion Prof to attempt parsing the logs even if gzip decode fails.
2. Issue a warning in Legion when profiling is requested and zlib is not available.

[elliottslaughter]

A fix for (1) is in https://gitlab.com/StanfordLegion/legion/-/merge_requests/1462.

Open question whether we want to warn users in this scenario, as the logs will not use disk space/bandwidth as efficiently.

[elliottslaughter]

MR 1462 has been merged, @mariodirenzo please confirm this fixes the immediate issue about parsing uncompressed logs.