fix: remove registry from publishConfig to allow dual publishing

- Remove hardcoded npm registry from package.json
- Allows workflow to control registry via setup-node registry-url
- Enables publishing to both npm and GitHub Packages
- Registry is now set by workflow, not package.json

Author: amannirala13

packages/cli/package.json

@@ -41,8 +41,7 @@
     "LICENSE"
   ],
   "publishConfig": {
-    "access": "public",
-    "registry": "https://registry.npmjs.org"
+    "access": "public"
   },
   "scripts": {
     "dev": "tsx watch src/cli.ts",

packages/runner-node/package.json

@@ -31,8 +31,7 @@
     "README.md"
   ],
   "publishConfig": {
-    "access": "public",
-    "registry": "https://registry.npmjs.org"
+    "access": "public"
   },
   "scripts": {
     "build": "tsup",