fix(pipeline): invalidate the yarn and node_modules cache when lockfile is changed
When updating node packages in a MR they get added to the same the GitLab CI/CD cache that a pipeline on tags or other MRs use. This might then cause build breakage on the other MRs and tag pipelines.
To fix this make the cache dependant on the yarn.lock
. If that file changes, a different cache is used.
Note: pipelines on the default branch are not affected due to Use separate caches for protected branches being enabled by default.