build: improve npm scripts to update package-lock.json upon install

[raymondfeng]

This is a follow-up improvement to #2593 and #2583:

1. Add update-package-locks script
2. Add update-packages to update greenkeeper.json and package-lock.json for individual packages.
3. The release script uses npm run ci to capture potential package-lock issues.

Checklist

👉 Read and sign the CLA (Contributor License Agreement) 👈

• npm test passes on your machine
• New tests added or existing tests modified to cover all changes
• Code conforms with the style guide
• API Documentation in code was updated
• Documentation in /docs/site was updated
• Affected artifact templates in packages/cli were updated
• Affected example projects in examples/* were updated

[bajtos]

@raymondfeng What happened to ci and postci scripts? You have removed them as part of the changes made from 8a4e887 to e5cb985.

  "ci": "npm ci --ignore-scripts && npm run -s postci",
  "postci": "lerna bootstrap --ci",

I really want to preserve fast install for local development. It was my understanding that the two lines above were ensuring that npm ci always runs fast npm ci in individual packages too. Without them, npm ci calls postinstall script which triggers slow clean & full reinstall.

[bajtos]

I measured time to install dependencies to see how bad the difference actually is.

Your feature branch as of e5cb985:

$ time npm i

> loopback-next@0.1.0 postinstall /Users/bajtos/src/loopback/next
> lerna bootstrap

(...)

real	0m5.613s
user	0m6.447s
sys	0m1.190s

Current master as of a56e911

$ time npm i

> loopback-next@0.1.0 postinstall /Users/bajtos/src/loopback/next
> lerna bootstrap && npm run -s update-greenkeeper-json

real	0m5.978s
user	0m6.823s
sys	0m1.261s

Just now I realized that you have actually reworked postinstall script to invoke lerna bootstrap, not the full clean+reinstall 🙈

[bajtos]