Parsing NPM registry from .npmrc should support scope-specific registries

[sschuberth]

Currently, readRegistryFromNpmRc() only supports "global" registries:

ort/analyzer/src/main/kotlin/managers/utils/NodeSupport.kt

Line 147 in db219fe

if (key == "registry") return value

But we should support the syntax for scope-specific registries, too, see

# last modified: 01 Jan 2016
; Set a new registry for a scoped package
@myscope:registry=https://mycustomregistry.example.org

[nicorikken]

Ah, thanks for raising this. Now I know why I couldn't get our custom npm package to work. To be explicit ORT is raising the following errors:

14:27:35.485 [DefaultDispatcher-worker-2] INFO  org.ossreviewtoolkit.analyzer.managers.Npm - Could not retrieve package information for '@alliander%2Falliander-plugin-xxx' from NPM registry https://registry.npmjs.org:  (HTTP code 404)

With the .npmrc file:

always-auth=true//npm.pkg.github.com/:_authToken=${NODE_AUTH_TOKEN}
@alliander:registry=https://npm.pkg.github.com/

If I understand it correctly, the npmRegistry variable is global, so this is quite a bit of rework.

[sschuberth]

This was obsoleted by #5162 which removed readRegistryFromNpmRc() altogether in favor of a better solution based on npm view.