fix(core): update yarn-parser to handle yarn v4 syntax

[a88zach]

Update the yarn-parser so that yarn.lock file generation works with yarn v4

Current Behavior

yarn.lock is not correctly created when using yarn v4

"":
  version: 1.22.8
  resolution: "resolve@patch:resolve@npm%3A1.22.8#optional!builtin<compat/resolve>::version=1.22.8&hash=c3c19d"
  dependencies:
    is-core-module: "npm:^2.13.0"
    path-parse: "npm:^1.0.7"
    supports-preserve-symlinks-flag: "npm:^1.0.0"
  bin:
    resolve: bin/resolve
  checksum: 0446f024439cd2e50c6c8fa8ba77eaa8370b4180f401a96abf3d1ebc770ac51c1955e12764cde449fde3fff480a61f84388e3505ecdbab778f4bef5f8212c729
  languageName: node
  linkType: hard

Expected Behavior

yarn.lock should be created correctly with no missing keys

Related Issue(s)

Fixes #19881

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Skipped Deployment

Name	Status	Preview	Updated (UTC)
nx-dev	⬜️ Ignored (Inspect)	Visit Preview	Nov 25, 2024 7:11pm

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 7769a3a. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution

---

✅ Successfully ran 4 targets

• nx affected --targets=lint,test,build,e2e,e2e-ci --base=6904789b1092e2591524d58f806e2004482750a2 --head=7769a3afa4618c841790d7f9eb9e620033eab172 --parallel=3
• nx run-many -t check-imports check-commit check-lock-files check-codeowners documentation --parallel=1 --no-dte
• nx-cloud record -- nx format:check --base=6904789b1092e2591524d58f806e2004482750a2 --head=7769a3afa4618c841790d7f9eb9e620033eab172
• nx documentation --no-dte

---

Sent with 💌 from NxCloud.

[a88zach]

The entries for yarn 3 follow this syntax:
resolve@patch:[email protected]#~builtin<compat/resolve>

The entries for yarn 4 follow this syntax:
resolve@patch:resolve@npm%3A1.22.8#optional!builtin<compat/resolve>

[a88zach]

@leosvelperez any thoughts on this one?

[github-actions]

This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request.