chmod is used instead of lchmod

Summary

When extracting cache that has symlinks the symlinked files throw a chmod error

WARNING: node_modules/@wek/clock: chmod node_modules/@wek/clock: no such file or directory (suppressing repeats)

it exists but is symlinked from a previous run. This then causes the following issue

npm WARN checkPermissions Missing write access to /builds/iues/wekwork-fe/node_modules/@wek/clock

Steps to reproduce

(How one can reproduce the issue - this is very important) Install npm packages Create a symlink from node_modules Run the build Re-Run build (bug is here due to caching of the symlink)

What is the current bug behavior?

chmod is used when lchmod should be used to avoid this error

What is the expected correct behavior?

symlinks from cache do not create permission problems while extracting the cache

Possible fixes

use lchmod in the runner cache extraction instead of chmod, so that symlinks do not create this problem.