Move known plugin package constants from cli-common to cli-internal

The known plugin package ID mappings don't need to be part of the
public API surface. Move them to @internal/cli and update consumers.

Signed-off-by: Patrik Oldsberg <poldsberg@gmail.com>
Made-with: Cursor

packages/cli-module-maintenance/package.json

@@ -19,6 +19,7 @@
   "license": "Apache-2.0",
   "main": "src/index.ts",
   "types": "src/index.ts",
+  "bin": "bin/backstage-cli-module-maintenance",
   "files": [
     "dist",
     "bin"
@@ -42,6 +43,5 @@
   "devDependencies": {
     "@backstage/cli": "workspace:^",
     "@types/fs-extra": "^11.0.0"
-  },
-  "bin": "bin/backstage-cli-module-maintenance"
+  }
 }

packages/cli-module-maintenance/src/commands/repo/fix.ts

@@ -29,11 +29,11 @@ import {
   relative as relativePath,
   extname,
 } from 'node:path';
+import { targetPaths } from '@backstage/cli-common';
 import {
-  targetPaths,
   knownBackendPluginPackageNameByPluginId,
   knownFrontendPluginPackageNameByPluginId,
-} from '@backstage/cli-common';
+} from '@internal/cli';
 
 const SCRIPT_EXTS = ['.js', '.jsx', '.ts', '.tsx', '.json'];