fix: migration CLI by making packages external

[nmerget]

Proposed changes

closes #3578
closes #3581

Types of changes

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Refactoring (fix on existing components or architectural decisions)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update (if none of the other choices apply)

Further comments

[github-actions]

🔭🐙🐈 Test this branch here: https://db-ui.github.io/mono/review/fix-migration-tool

[mfranzke]

@nmerget this might only fix #3581 instead of #3578, doesn't it? Or do you actually expect both to be fixed?

[nmerget]

It should fix both, yes

[mfranzke]

It should fix both, yes

you're the best

[mfranzke]

It should fix both, yes

@nmerget düümm düümmm

node:internal/modules/esm/resolve:854
  throw new ERR_MODULE_NOT_FOUND(packageName, fileURLToPath(base), null);
        ^

Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'commander' imported from /Users/maximilianfranzke/.npm/_npx/0d1f7af59eae6113/node_modules/@db-ui/foundations/build/index.js
    at packageResolve (node:internal/modules/esm/resolve:854:9)
    at moduleResolve (node:internal/modules/esm/resolve:927:18)
    at defaultResolve (node:internal/modules/esm/resolve:1169:11)
    at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:383:12)
    at ModuleLoader.resolve (node:internal/modules/esm/loader:352:25)
    at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:227:38)
    at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:87:39)
    at link (node:internal/modules/esm/module_job:86:36) {
  code: 'ERR_MODULE_NOT_FOUND'
}

Node.js v20.16.0

[nmerget]

We need to publish the migration under another name. The problem is that we need dependencies from package.json to install something like commander in npx. But we shouldn't install it for @db-ui/foundations

[mfranzke]

We need to publish the migration under another name. The problem is that we need dependencies from package.json to install something like commander in npx. But we shouldn't install it for @db-ui/foundations

be my guest. Judged by the statistics you haven't opened another repo (or at least another package) this week (who are you and what did you do to @nmerget btw.?). I would assume that we could keep it in this repo, but call it @db-ui/migration than ?