fix(test, monitor): use --strict-out-of-sync when set to false with pnpm for top level dependencies

[gemaxim]

Pull Request Submission Checklist

• Follows CONTRIBUTING guidelines
• Includes detailed description of changes
• Contains risk assessment (Low | Medium | High)
• Highlights breaking API changes (if applicable)
• Links to automated tests covering new functionality
• Includes manual testing instructions (if necessary)
• Updates relevant GitBook documentation (PR link: ___)

What does this PR do?

Bumps nodejs-lockfile-parser and snyk-nodejs-plugin with a fix in pnpm for --strict-out-of-sync=false option. Previously, even though this option was set to false, we would still throw the error for top level dependencies.
Changes in this PR: snyk/nodejs-lockfile-parser#261.

Where should the reviewer start?

Tests in the lockfile parser are included in the above PR for all lockfile versions.
Updated acceptance test for pnpm in this cli PR.

How should this be manually tested?

Create a project with files included in the fixtures ( example ). Run snyk test --strict-out-of-sync=false succesfully. snyk test should fail with OutOfSync error.

[github-actions]

	Warnings
⚠️	"fix: use --strict-out-of-sync when set to false with pnpm for top level dependencies" is too long. Keep the first line of your commit message under 72 characters.

Generated by 🚫 dangerJS against 8d5b71a

[thisislawatts]

Issue(blocking): Could you reword the commit slightly, so it will be easier to read when compiled into our release notes. For example:
fix: use --strict-out-of-sync when set to false with pnpm for top level dependencies