feat(nodejs): parse licenses in yarn projects

[nikpivkin]

Description

At the moment, dependency licenses in projects with the yarn package manager are not parsed. This pr adds license scanning for packages from the cache folders .yarn (for yarn 2+) and node_modules (yarn classic). The license field is also checked, because it can refer to a file and then it is necessary to classify the license. (npm/npm#8795 (comment), https://docs.npmjs.com/cli/v9/configuring-npm/package-json#license)

Related issues

• Close feat(nodejs): parse licenses in yarn projects #4811

Checklist

• I've read the guidelines for contributing to this repository.
• I've followed the conventions in the PR title.
• I've added tests that prove my fix is effective or that my feature works.
• I've updated the documentation with the relevant information (if needed).
• I've added usage information (if the PR introduces new options)
• I've included a "before" and "after" example to the description (if the PR is a user interface change).

[DmitriyLewen]

Nice work!
I left few small comments.
@nikpivkin take a look, when you have time, please.

[DmitriyLewen]

I have 1 question:
If package is installed in workspace - does yarn still create copy/link of package.json file in node_mosules/.yarn folder?
Can you check this case?

Could you also update nodejs page in docs, please.

[nikpivkin]

@DmitriyLewen yarn has only 1 node_modules/.yarn folder in the root of the project, so all the dependencies of the workspaces are there.

[DmitriyLewen]

ok, thanks for the clarification!

[DmitriyLewen]

@nikpivkin left some comments

[DmitriyLewen]

LGTM.
@nikpivkin I left 1 comment about debug message. Can you take a look?

[DmitriyLewen]

LGTM