chore: move next admin packages to core repo (#5983)

**What**
- Move packages for `next` version of admin to core repo

**Other**
- Since this PR introduces packages that depend on Vite 5, it also introduces @types/node@^20. We have never had a direct dependency on the types package for Node, and as far as I can see that has resulted in us using the types from Node.js@8, as those are a dependency of one of our dependencies. With the introduction of @types/node@^20, two of our packages had TS errors because they were using the NodeJS.Timer type, which was deprecated in Node.js@14. We should add specific @types/node packages to all our packages, but I haven't done so in this PR to keep it as clean as possible.
- Q: @olivermrbl I've added the new packages to the ignore list for changeset, is this enough to prevent them from being published?

packages/admin-next/admin-bundler/package.json

@@ -0,0 +1,34 @@
+{
+  "name": "@medusajs/admin-bundler",
+  "version": "0.0.0",
+  "scripts": {
+    "build": "rimraf dist && tsup"
+  },
+  "bin": {
+    "medusa-admin": "./bin/medusa-admin.js"
+  },
+  "main": "dist/index.js",
+  "types": "dist/index.d.ts",
+  "module": "dist/index.mjs",
+  "files": [
+    "dist"
+  ],
+  "devDependencies": {
+    "rimraf": "5.0.1",
+    "tsup": "^8.0.1",
+    "typescript": "^5.3.3"
+  },
+  "dependencies": {
+    "@medusajs/ui-preset": "^1.0.2",
+    "@medusajs/vite-plugin-extension": "*",
+    "@vitejs/plugin-react": "^4.2.1",
+    "autoprefixer": "^10.4.16",
+    "commander": "^11.1.0",
+    "deepmerge": "^4.3.1",
+    "glob": "^7.1.6",
+    "postcss": "^8.4.32",
+    "tailwindcss": "^3.3.6",
+    "vite": "5.0.10"
+  },
+  "packageManager": "yarn@3.2.1"
+}