Don't write cache path into yarn.lock for nested file dependencies

[sokki]

Summary

Solves #4388
Based on #4717

The linked issue is unresolved for over a year now. It seems like solving the root cause of this issue by bypassing the cache for file-dependencies would require too much refactoring of the underlying architecture. At least I got lost while trying to do so 🙃

So I chose this rather naive approach. All tests pass and I've tested it in a bigger monorepo where we regularly faced this issue.

Test plan
What was written to yarn.lock before:

[buildsize]

File name	Previous Size	New Size	Change
yarn-[version].noarch.rpm	1.11 MB	1.11 MB	567 bytes (0%)
yarn-[version].js	4.47 MB	4.47 MB	1.33 KB (0%)
yarn-legacy-[version].js	4.66 MB	4.66 MB	1.57 KB (0%)
yarn-v[version].tar.gz	1.12 MB	1.12 MB	97 bytes (0%)
yarn_[version]all.deb	815.67 KB	815.75 KB	76 bytes (0%)

[arcanis]

The 1.15 will have a fair amount of changes already, so I'd like to postpone this to the 1.16 if you don't mind (since it might have unseen side effects) 😃

[sokki]

Sure. As long as we don't have to wait for berry 🙃

[arcanis]

Nope, no worry, I keep merging PRs over here 😉

[krigar1184]

Any chance for this to be merged any time soon?

[desaiuditd]

@arcanis When this PR is scheduled to be merged?