Add check in CI to ensure that if a new package is added it starts off at 0.0.0

[mcmire]

When a new package is added and it does not start out as 1.0.0, this can break releases because the publish-release will think it's a new release and expect there to be a section in the changelog for the new release, and when it does not find one (because any new entries start out in Unreleased) it will fail.

We should add a check to ensure that no PR that introduces a new package can be merged if the version of that package is not 0.0.0.

[mcmire]

Ideally, in a release PR we should try to run publish-release (or a dry-run version) of it, as well as npm-publish, in CI as well too, just to ensure that there won't be any issues when we try to run them for real after the PR is merged.