Rename the top-level publish command to publish:all to not confuse lerna.

It seems that this is being invoked even when we don’t want, so we’ll make sure it has a different name than the standard ‘publish’ command.

package.json

@@ -39,7 +39,7 @@
     "lint": "jlpm && jlpm run prettier && jlpm run eslint && jlpm run tslint",
     "lint:check": "jlpm run prettier:check && jlpm run eslint:check && jlpm run tslint:check",
     "patch:release": "node buildutils/lib/patch-release.js",
-    "publish": "jlpm run pre-publish && lerna publish --force-publish=* -m \"Publish\"",
+    "publish:all": "jlpm run pre-publish && lerna publish --force-publish=* -m \"Publish\"",
     "publish:next": "jlpm run pre-publish && lerna publish --npm-tag=next --force-publish=* -m \"Publish with 'next' tag\"",
     "publish:next:changed": "jlpm run pre-publish && lerna publish --npm-tag=next -m \"Publish with 'next' tag\"",
     "publish:next:from-git": "jlpm run pre-publish && lerna publish from-git --npm-tag=next",