feat(auth): Support two factor authentication for NPM accounts

[neonowy]

Summary
Added support for logging into NPM account with 2FA enabled, based on npm-profile implementation.
Fixes #4904.

Test plan

1. Enable 2FA for your account: https://docs.npmjs.com/getting-started/using-two-factor-authentication
2. Run yarn publish:

Issues
I've added some basic tests, but don't know where should I put functional test with the whole one-time password prompt flow (like in the screenshot above). Are there any similar high-level tests you could point me to?

I also don't support --non-interactive, because AFAIK there's no way to access Config nor flags (Do we need to check both of them?) from NpmRegistry.request(...), as it's done in the case of getToken(config, reporter, name, flags, registry) which is always called directly inside run(config, reporter, flags, args) function:

yarn/src/cli/commands/login.js

Lines 65 to 68 in aa4e713

	// make sure we're not running in non-interactive mode before asking for login
	if (flags.nonInteractive || config.nonInteractive) {
	throw new MessageError(reporter.lang('nonInteractiveNoToken'));
	}

I see two possible solutions here:

1. Add Config/flags (both?) to the arguments of NpmRegistry.request(...):
   

   yarn/src/registries/npm-registry.js

   Line 136 in aa4e713

   request(pathname: string, opts?: RegistryRequestOptions = {}, packageName: ?string): Promise<*> {

2. Handle catching OneTimePasswordError with every call of npm.request(...), which could unnecessary obfuscate run(...) functions.

Any feedback would be appreciated ✌️

[buildsize]

File name	Previous Size	New Size	Change
yarn-[version].noarch.rpm	1.09 MB	1.09 MB	686 bytes (0%)
yarn-[version].js	4.27 MB	4.27 MB	2.14 KB (0%)
yarn-legacy-[version].js	4.44 MB	4.44 MB	3.5 KB (0%)
yarn-v[version].tar.gz	1.1 MB	1.1 MB	422 bytes (0%)
yarn_[version]all.deb	804.62 KB	804.99 KB	386 bytes (0%)

[arcanis]

Thanks for your work! I made a first read and it already looks quite good 👍

I also don't support --non-interactive, because AFAIK there's no way to access Config nor flags (Do we need to check both of them?) from NpmRegistry.request(...)

Hm, I wonder whether the best wouldn't be for the interactive flag to be part of the reporter rather than the configuration 🤔

[arcanis]

Ok, looks good to me!

Since you seem to have unticked the box allowing me to make edits to your PR, can you rebase and update the CHANGELOG.md file? Thanks! 🙂

[arcanis]

Ah, my bad - I could change it, Github was just still suffering from today's data failure