Pin npm registry explicitly in publish-version

yarn version's postversion hook was inheriting yarn's default
npm_config_registry (registry.yarnpkg.com) into the npm publish
subprocess, causing ENEEDAUTH against the wrong registry.

Author: xdevanshux

bin/publish-version

@@ -59,7 +59,7 @@ fi
 
 for pkg in ./modules/*; do
   if [[ -d $pkg ]]; then
-    npm publish --access public --tag next --provenance $pkg
+    npm publish --access public --tag next --provenance --registry https://registry.npmjs.org/ $pkg
   fi
 done