npm-run: fix commands with whitespaces on windows

Fixes #4403
npmconf@0.1.11
npmconf@0.1.12
npm-registry-client@0.3.3
Change the way how tests fail on stderr output.

Wait whole message from stderr output and only after that throw error. This helps to get whole picture why test fails.
node-gyp@0.12.2
init-package-json update

For promzard license, mostly
sha update

For new readable-stream
Revert "prune: --production option to unbuild devDependencies"

This reverts commit f65da7d7f156fd28db10042a8db6682ef70178a7.

See #4509
rimraf@2.2.6
read-package-json@1.1.6
adduser: All defaults are empty strings if unfound
v1.3.24
Remove gubblebum blocky font

It makes the headings in the html docs kind of hard to read, and also
distributing the font file in this way has some awkward IP issues.

(Using the font for the npm logo graphical asset is fine, only
distributing the font file itself is problematic.)
Don't publish webfonts we don't have
v1.3.25
npm-registry-client@0.3.5
Typo, "err" variable name should be "er".
publishConfig: conf.save() should save actual config, not pubConf

This avoids an error when the npm-registry-client gets a new token, and
attempts to call conf.save('user').  However, a publishConfig can't save
in this way, because it doesn't have a 'user' file source.

Binding the save to the parent config *does* avoid the error, but of course,
at the cost of making the save in this situation a no-op.
v1.3.26