yarn pack on Windows doesn't put execute permissions on directories

[nborko]

Bug description

Running yarn pack on Windows creates a tarball that doesn't include execute permissions on directories.

Command

yarn pack

What is the current behavior?
All directories and files are 0666. It's understandable that executable files may not be executable, even under git-bash, but the resulting tarball cannot be extracted in a POSIX environment due to incorrect directory permissions.

What is the expected behavior?
Tarballs generated from yarn pack in Windows should be extractable everywhere tar is supported.

Steps to Reproduce
Run yarn pack on Windows, copy the tarball to Linux, MacOS X, etc., and tar zxf package-version.tgz

Environment

• Node Version: v12.14.1
• Yarn v2 Version: 1.22.4 (yarn v1 also exhibits this behavior)
• OS and version: Windows 10 Pro 1909 18363.815

[pauldraper]

Yikes, I just ran into this with StreakYC/react-draggable-list#67

It made it impossible to extract the tarball on Linux (without some extra funkiness at least).