chore: removes restore-keys from yarn install to prevent cache pollution

[christopherferreira9]

Description

Recently, we've noticed that cache was getting polluted. The restore-keys was acting as a fallback for when the actual key was found so in scenarios where a dependency would be bumped and merged into main, other side branches that were not updated with main would get this bundle.

Evidences

On mobile, commit dea4f71aea67372b084ad45359c60bd2caf38d58 (calling 1 coming forward) is behind 70335d9db18a6a8e055147dca032f906c60e15be (calling 2 coming forward).

Timeline

• 2 runs CI and cache for yarn is not found: https://github.com/MetaMask/metamask-mobile/actions/runs/21596601924/job/62232652684#step:5:685
  • cache is not found for e2e-yarn-android-Linux-a78efe101674666ffc020b3d0bec0b0361da011aca46ef4a6427a45b40fcab84
• 2 merges into main a ramps-controller change from 4.1.0 to 5.0.0 (diff)
• 1 is still behind main and triggers CI
  • on the setup-e2e-env you can see that the cache hit comes from a restore-key: https://github.com/MetaMask/metamask-mobile/actions/runs/21598477057/job/62240511560?pr=25470#step:5:688
  • a live call coming from the ramps-controller happens using controller version 5.0.0 -> https://github.com/MetaMask/metamask-mobile/actions/runs/21598477057/job/62240511560?pr=25470#step:15:127
  • the key restored here is a78efe101674666ffc020b3d0bec0b0361da011aca46ef4a6427a45b40fcab84 which was generated after 2 was merged into mai

Reference links:

• Failed run behind of main: https://github.com/MetaMask/metamask-mobile/actions/runs/21598477057/job/62240511560?pr=25470
  • ramps controller version at the time of the run that failed: https://github.com/MetaMask/metamask-mobile/blob/dea4f71aea67372b084ad45359c60bd2caf38d58/package.json#L271
• Pr that introduced the controller dependency bump: feat(ramps): adds tokens, providers & paymentMethods to ramps controller state metamask-mobile#25296
  • ramps controller version after merging MetaMask/metamask-mobile@70335d9#diff-7ae45ad102eab3b6d7e7896acd08c427a9b25b346470d7bc6507b6481575d519

---

Note

Low Risk
Low risk workflow change; it only affects CI cache restore behavior and may increase cache misses but avoids reusing stale node_modules across divergent branches.

Overview
Removes restore-keys from the actions/cache step for the E2E Yarn node_modules cache in .github/actions/setup-e2e-env/action.yml, ensuring caches are only restored on an exact yarn.lock hash match.

This prevents fallback cache hits from older keys that could introduce stale dependencies and "pollute" CI runs across branches.

^{Written by Cursor Bugbot for commit 44e3ced. This will update automatically on new commits. Configure here.}