Release tooling: Make canaries use v0.0.0

[JReinhold]

What I did

The current versioning for canary releases means that users specifying a prerelease dependency with a caret, eg. @storybook/cli@^7.2.0-alpha.0 will end up getting a canary release for that, because npm treats the "c" in "canary" as later than the "a" in "alpha".
This PR publishes canaries to v0.0.0 to fix that.

How to test

See the canary release of this PR at https://github.com/storybookjs/storybook/actions/runs/5666847429/job/15354420488

Checklist

• Make sure your changes are tested (stories and/or unit, integration, or end-to-end tests)
• Make sure to add/update documentation regarding your changes
• If you are deprecating/removing a feature, make sure to update
  MIGRATION.MD

Maintainers

• When this PR is ready for testing, make sure to add ci:normal, ci:merged or ci:daily GH label to it to run a specific set of sandboxes. The particular set of sandboxes can be found in code/lib/cli/src/sandbox-templates.ts
• Make sure this PR contains one of the labels below.

["cleanup", "BREAKING CHANGE", "feature request", "bug", "build", "documentation", "maintenance", "dependencies", "other"]

🦋 Canary release

This pull request has been released as version 0.0.0-pr-23609-sha-f47ef339. Install it by pinning all your Storybook dependencies to that version.

More information

Published version	0.0.0-pr-23609-sha-f47ef339
Triggered by	@JReinhold
Repository	storybookjs/storybook
Branch	fix-canary-versions
Commit	f47ef339
Datetime	Wed Jul 26 09:07:49 UTC 2023 (1690362469)
Workflow run	5666847429

To request a new release of this pull request, mention the @storybookjs/core team.

core team members can create a new canary release here or locally with gh workflow run --repo storybookjs/storybook canary-release-pr.yml --field pr=23609

[vanessayuenn]

LGTM 🚢