build: improve lerna publish process

[erickzhao]

Motivation

We don't leverage our conventional commit usage to help automate versioning.

Changes

Wraps the lerna publish command into a new lerna:publish npm script with additional configuration to address the two issues above.

• --conventional-commits: Auto-selects the package number for us.
• --no-changelog: Seems like the changelog generated is per package, which we don't want. Let's keep doing this step manually.

Having this in a command within the repo helps in two ways:

1. Less human error possible by forgetting a flag by accident.
2. Lerna version matches our devDependencies rather than being a globally installed NPM package.

I also changed the root package.json version number to 0.0.0-development since Lerna doesn't update the root package.json number by default and our version number was stale. There's a workaround that involves adding the root folder as a package itself, but then you have to run each lerna command with --no-private which is annoying and not worth it IMO.

Testing

I tested this manually by running lerna version --no-push --no-git-tag-version --force-publish --conventional-commits --no-changelog, which is as close to a dry run as possible since Lerna does not yet support dry runs.

[VerteDinde]

Looks great, thanks for fixing this!