ci: Fix update workflow to use latest yarn.lock changes

[Mrtenz]

Currently we cache the node_modules folder and restore it from cache in the steps after. This means that any changes to the yarn.lock file made in the deduplication step are not used for generating LavaMoat policies or building the examples, sometimes resulting in errors.

To fix it, I've added a check which checks if the yarn.lock was updated. The other steps will use a high risk environment which skips loading the node_modules cache if that's the case.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.06%. Comparing base (75acad8) to head (7ac1e25).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #3379   +/-   ##
=======================================
  Coverage   98.06%   98.06%           
=======================================
  Files         397      397           
  Lines       10929    10929           
  Branches     1720     1720           
=======================================
  Hits        10718    10718           
  Misses        211      211           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.