Follow-up on follow-up 293e28d with more package-lock.json changes.

When I first generated this change by running `npm install`, I'd done it
after running `npm run clean`, which I periodically do when changing
branches.  One of the things which the `npm run clean` command does is wipe
the `node_modules` directory, which leaves `npm install` in a position of
reinstalling it from scratch, rather than leveraging any of the existing
cached metadata which exists within that `node_modules` tree.

While the first invocation of `npm install` did generate the delta in
293e28d, a follow-up invocation (without a `npm run clean`; running `npm
install` twice in a row) did generate the additional changes contained
within this commit, which must be getting introduced into the `node_modules`
tree after Lerna does its hoisting (but after `npm` has written its first
pass at `package-lock.json`).

This is admittedly a bit annoying.

cc @glasser

Ref: 293e28d300b#commitcomment-34486618