pnpm 7.4.0-2 on Node.js NPM

Minor Changes

Dependencies patching is possible via the pnpm.patchedDependencies field of the package.json.
To patch a package, the package name, exact version, and the relative path to the patch file should be specified. For instance:
```
{
  "pnpm": {
    "patchedDependencies": {
      "eslint@1.0.0": "./patches/eslint@1.0.0.patch"
    }
  }
}
```
Two new commands added: pnpm patch and pnpm patch-commit.
pnpm patch <pkg> prepares a package for patching. For instance, if you want to patch express v1, run:
```
pnpm patch express@1.0.0
```
pnpm will create a temporary directory with express@1.0.0 that you can modify with your changes.
Once you are read with your changes, run:
```
pnpm patch-commit <path to temp folder>
```
This will create a patch file and write it to <project>/patches/express@1.0.0.patch.
Also, it will reference this new patch file from the patchedDependencies field in package.json:
```
{
  "pnpm": {
    "patchedDependencies": {
      "express@1.0.0": "patches/express@1.0.0.patch"
    }
  }
}
```
package-import-method supports a new option: clone-or-copy.
New setting added: include-workspace-root. When it is set to true, the run, exec, add, and test commands will include the root package, when executed recursively #4906

Don't crash when pnpm update --interactive is cancelled with Ctrl+c.
The use-node-version setting should work with prerelease Node.js versions. For instance:
```
use-node-version=18.0.0-rc.3
```
Return early when the lockfile is up-to-date.
Resolve native workspace path for case-insensitive file systems #4904.