CLI should be able to use a token for a scope only

[lukekarrys]

Problem Statement

The CLI should be able to use additional tokens for a single registry and separate them by scope. This is not currently possible. Meaning if you have public and private scoped packages on the same registry, you must use the same token for both.

Possible Solution

.npmrc

//registry.npmjs.org/:_authToken=<TOKEN_A>
registry=https://registry.npmjs.org/
@npmcorp:_authToken=<TOKEN_B>
@npm:registry=https://npm.pkg.github.com/
//npm.pkg.github.com/:_authToken=<TOKEN_C>

Given the above .npmrc file the CLI should be able to run the following commands:

npm publish semver # would use TOKEN_A on https://registry.npmjs.org/
npm install @npmcorp/hello # would use TOKEN_B on https://registry.npmjs.org/
npm install @npm/hello # would use TOKEN_C for https://npm.pkg.github.com/