fix: avoid bundling svelte/compiler for analytics version

[smart]

Summary

• replace the svelte/compiler import in config.ts with VERSION from svelte to avoid pulling compiler code into client bundles
• make version normalization resilient when runtime VERSION is unavailable by falling back to 0.0.0
• update the svelte mock in config.test.ts to include VERSION

Test plan

• node packages/svelte-cloudinary/scripts/version.js
• pnpm --filter svelte-cloudinary test
• pnpm --filter svelte-cloudinary build

Made with Cursor

[vercel]

@smart is attempting to deploy a commit to the Cloudinary DevX Team on Vercel.

A member of the Team first needs to authorize it.

[changeset-bot]

⚠️ No Changeset found

Latest commit: ec31cf3

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

[ghostdevv]

This doesn't seem to be the right fix, as I don't think VERSION is exported from the root svelte package even in v5