Do not output messages about unrelated, unsupported, optional dependencies

[bjornstar]

$ npm -v
3.8.0
$ cat package.json
{
  "name": "notsup-repro",
  "version": "1.0.0",
  "description": "Reproduce not supported annoyance",
  "main": "index.js",
  "license": "ISC",
  "repository": "make-it-stop-complaining"
  "dependencies": {
    "chokidar": "^1.4.3"
  }
}
$ npm install object-assign --save
npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: fsevents@1.0.8
$ echo $?
0

object-assign does not have any dependencies. npm should not be warning us about an unrelated, unsupported, and optional package: chokidar/fsevents

Somewhat related: #10768 and #11632

We should not receive any output from npm about a package that we are not currently installing.

[bjornstar]

$ npm -v
3.10.8
$ cat package.json
{
  "name": "notsup-repro",
  "version": "1.0.0",
  "description": "Reproduce not supported annoyance",
  "main": "index.js",
  "author": "please",
  "repository": "make-it-stop-complaining",
  "license": "ISC",
  "dependencies": {
    "chokidar": "^1.4.3"
  }
}
$ npm install object-assign --save
notsup-repro@1.0.0 /home/bjorn/notsup-repro
└── object-assign@4.1.0 

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.0.14: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

The word failed has been removed, but now we have warnings about unrelated, unsupported, optional packages in ALL CAPS.

[npm-robot]

We're closing this issue as it has gone seven days without activity and without being labeled. If we haven't even labeled in issue in seven days then we're unlikely to ever read it.

If you are still experiencing the issue that led to you opening this or this is a feature request you're still interested in then we encourage you to open a new issue. If this was a support issue, you may be better served by joining package.communty and asking your question there.

For more information about our new issue aging policies and why we've instituted them please see our blog post.