feat: add option to disable the node_modules scan for node.js images

[adrobuta]

• Ready for review
• Follows CONTRIBUTING rules
• Reviewed by Snyk internal team

What does this PR do?

Before v6.12.0, the docker cli plugin was able to scan npm projects only when strict package.json and package-lock.json pairs of files were identified within container images. The pair of files had to be outside of a node_modules folder’s context in order to avoid creating projects out of the dependencies. Scanning container images that had the manifests/lockfiles removed was not possible and customer needs were created to remove that constraint.

The scanning of npm global and local scoped node_modules directories has been enabled as a default behavior when a node.js image is scanned.
Adding an option to opt-out from the node_modules scan allows the user to scan npm projects only when [strict package.json and package-lock.json pairs are identified in the container image, thus re-enabling the original npm scan behavior.

Where should the reviewer start?

How should this be manually tested?

Any background context you want to provide?

What are the relevant tickets?

Screenshots

Additional questions