Remove resolving with 401 status code

[Fer0x]

Summary

When registry returns 401 status code it should be considered as error.
401 means that credentials are invalid, but yarn says that everything is fine.

#6413 - this PR didn't change handling of 401 errors.

Test plan

yarn publish with expired/corrupted token in .npmrc.

[buildsize]

File name	Previous Size	New Size	Change
yarn-[version].js	[new file]	4.2 MB
yarn-[version].noarch.rpm	[new file]	1.07 MB
yarn-legacy-[version].js	[new file]	4.37 MB
yarn-v[version].tar.gz	[new file]	1.07 MB
yarn_[version]all.deb	[new file]	791.07 KB

[arcanis]

It seems like the 401 handling was added as part of #1558. Can you check that the use case described there (cloning from a private bitbucket repository) still works, before we merge this?

[Fer0x]

@arcanis ok, I'll look into it ASAP.

[Fer0x]

@arcanis

Command yarn-local add bitbucket:Lucus/test-npm-lib --verbose (private repo) works good for me.

[Fer0x]

@arcanis is there any reasons to not merge this PR? :)

[arcanis]

My workload, mostly 😅 will try to get a look today

[timemachine3030]

+1 for this to be resolved. Running yarn with a bad token in ~/.npmrc (or other location parsed by yarn) returns an inaccurate response:

$ yarn yarn install v1.16.0 info No lockfile found. [1/4] 🔍 Resolving packages... error Couldn't find package "typescript" on the "npm" registry. info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command. 

[jKatt]

I lately ran into this issue with an expired token and yarn silently ignoring it when publishing.

Are there any plans on merging this PR in the near future?

[Fer0x]

@arcanis Hey, what about merging this? ;)