[BUG] npm link does not inform about symlinked packages to global node_modules anymore

Current Behavior:

On a project with bin field in package.json, run npm link.

/path/to/project/package.json
{
  "name": "@my-package/cli",
  "bin": {
    "my-package-cli": "./bin/cli"
  }
}

/path/to/project $> npm link

up to date, audited x packages in 1s

found 0 vulnerabilities

Expected Behavior:

There's a message with files symlinked to global node_modules

/path/to/project/package.json
{
  "name": "@my-package/cli",
  "bin": {
    "my-package-cli": "./bin/cli"
  }
}

/path/to/project$> npm link

/path/to/global/node_modules/my-package-cli -> /path/to/project

up to date, audited x packages in 1s

found 0 vulnerabilities

Steps To Reproduce:

1. Start a new project

   /path/to/project/package.json
   {
     "name": "@my-package/cli",
     "version": "0.1.0",
     "bin": {
       "my-package-cli": "./bin/cli"
     }
   }
   

   /path/to/project/bin/cli
   #!/usr/bin/env node
   
   console.log('Hello!')
   

2. Run npm link from package directory
3. Expect message displaying which paths were symlinked

Environment:

• OS: macOS 10.15.7
• Node: 14.16.1
• npm: 7.11.2

Reproduce the issue with the package.json containing the bin mapping and the bin/cli entry point, then run npm link from the package directory. Trace the npm link command's output and verify that completion reports the paths symlinked into global node_modules.