fix: use wildcard for legacy package lingo.dev dependency

Legacy packages are deprecated wrappers that should always use the
latest lingo.dev version. Using wildcard (*) allows them to resolve
to the local workspace version without breaking CI when version bumps
happen via changesets.

This fixes the frozen-lockfile error in CI after version bumps.

Author: maxprilutskiy

legacy/cli/package.json

@@ -22,7 +22,7 @@
   "author": "",
   "license": "Apache-2.0",
   "dependencies": {
-    "lingo.dev": "0.117.0"
+    "lingo.dev": "*"
   },
   "deprecated": "Replexica is now Lingo.dev! Please use our new CLI package by running: npx lingo.dev@latest. Visit https://lingo.dev for the latest features and documentation."
 }

legacy/sdk/package.json

@@ -16,7 +16,7 @@
   "author": "",
   "license": "Apache-2.0",
   "dependencies": {
-    "lingo.dev": "0.117.0"
+    "lingo.dev": "*"
   },
   "deprecated": "Replexica is now Lingo.dev! Please use our new SDK package by running: npm install lingo.dev. Visit https://lingo.dev for the latest features and documentation."
 }