fix: checking if symlink with same prefix points outside the directory

[mmaietta]

If a directory is pointed to by a symbolic link whose name is the prefix of the directory, the directory won't be included in the asar. For example, the directory aa won't be included.

├── a -> aa
└── aa

Added a check (and test case) to see if the symlink is actually to a different directory and not a file (e.g. startsWith) within the symlinked dir. New test case mirrors test/input/packthis-with-symlink but with the symlink having the same prefix of a directory outside the symlink

Fixes: #303

[BlackHole1]

LGTM

[mmaietta]

Thanks @BlackHole1 ! Would you mind also taking a look at this PR? It's the same style of fix but for asar unpacking: #333

[BlackHole1]

@mmaietta Already approved! Thank you for the fix you submitted!
In general, we do not merge PRs immediately (unless they are very simple or submitted by a bot for dependency updates). We usually wait a few days to allow other maintainers to provide their input.

[continuous-auth]

🎉 This PR is included in version 3.2.17 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀