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

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.

Start by locating the CI workflow and the publish-release logic referenced in the issue, then trace how newly added packages and their versions are detected. The work is done when CI rejects a new package with a version other than 0.0.0 while allowing a package that starts at 0.0.0.

Written by the indexing model from the issue text.