Describe the bug

The changes between 8.7.60 and 8.7.61 treat permissions on files and directories simplistically and these prevent modules from loading.

I've confirmed that the problem is still present in 8.7.65.

To Reproduce

I have a module tree with two directories and both of these have a blank file 1.4.18.lua in them

$ ls -l modules
total 2
drw---S---+ 2 branfosj nobody 4096 Sep 25 10:28 M4
drwx--s--x+ 2 branfosj nobody 4096 Sep 23 14:03 M4.orig

In Lmod 8.7.60 both of these modules are loadable (module load M4/1.4.18 M4.orig/1.4.18).

In Lmod 8.7.61 I can load M4.orig/1.4.18 but module load M4/1.4.18 results in

Lmod has detected the following error:  These module(s) or extension(s) exist but cannot be loaded as requested: "M4/1.4.18"
   Try: "module spider M4/1.4.18" to see how to load the module(s).

If I do chmod +x M4 then I can load the module.

Additional context

We have our module tree on a GPFS file system. The above permissions are the result of some GPFS ACLs being changed overtime. But this leads to a possibility that the ACLs give file access that is not visible from the linux permissions.