Epic: Resolve npm --global issues

[lukekarrys]

Epic

Some commands have issues when run with the global --flag. I thought it would be helpful to gather all of these issues that I could find since from an initial look it seems like there will be some discussion and fixes that apply across multiple issues.

• [BUG] npm update -g package@latest removes all global packages cli#3175
• [BUG] npm list -g doesn't display a specific globally installed package, ESLint cli#3877
• [BUG] npm outdated should ignore private packages installed globally cli#3825
• [BUG] Cannot upgrade from v6 to v7 on windows 10 cli#3740
• [BUG] npm install -g . with a NPM_CONFIG_PREFIX results in ENOENT cli#3580
• [BUG] EINVALIDPACKAGENAME on npm update -g cli#2835
• [BUG] npm outdated -g outputs that it wants to upgrade to a new major version cli#3612
• Global Install from git repository fails when using 'prepare' script and 'bin' path cli#3692
• [BUG] global npm update from 7.13.0 to 7.16.0 in some configuration changes ownership of all files in /usr/local/bin cli#3375
• [BUG] installing a package globally from a directory with local dependencies can fail cli#2849
• [BUG] install fails with --offline and --global cli#3764
• [BUG] npm install -g doesn't install local dependencies in v7 cli#2968
• [BUG] npm update -g shows audit message that wont work cli#3830
• [BUG] Global install shows funding message but can't get info cli#3112
• [BUG] global update fails on windows cli#2838

[ljharb]

In particular, commands like update, that ostensibly work with package.json and/or a lockfile, seem like they're a category error for --global.

[dominykas]

I suspect npm/cli#3910 belongs on this list as well...

[wraithgar]

#3764 was a misunderstanding of how the cache worked.