Fix release CI

[simolus3]

Recent runs of the release CI are broken because we try to fetch a version we're about to potentially release from npm (we should be using the local version instead because the updated version obviously doesn't exist yet).

This can be reproduced locally by running pnpm changeset version && pnpm install --lockfile-only --frozen-lockfile=false. I don't understand why this is only happening for the react-supabase-todolist-tanstackdb demo, but it can be fixed by adding an explicit workspace dependency on @powersync/common. I'm a bit surprised the other demos don't need that because I don't see what's different about the tanstack demo, but this seems to fix it.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 98bb9be

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[stevensJourney]

I'm also not sure why this is an issue for this specific demo