fix(backend-dynamic-feature-service): improve package resolution for bundled dynamic plugins

Updated `resolvePackagePath` to correctly resolve `package.json` for dynamic plugins that bundle their own copy of `@backstage/backend-plugin-api`. This change ensures that the resolution works for both the host application and bundled dependencies, enhancing compatibility with plugins created using the `backstage-cli package bundle` command.

Signed-off-by: David Festal <dfestal@redhat.com>
Assisted-by: Cursor

packages/cli-module-build/cli-report.md

@@ -38,7 +38,6 @@ Options:
 
 Commands:
   build
-  bundle
   clean
   help [command]
   postpack
@@ -61,22 +60,6 @@ Options:
   -h, --help
 ```
 
-### `backstage-cli-module-build package bundle`
-
-```
-Usage: @backstage/cli-module-build package bundle
-
-Options:
-  --clean
-  --no-build
-  --no-install
-  --output-destination <string>
-  --output-name <string>
-  --pre-packed-dir <string>
-  --verbose
-  -h, --help
-```
-
 ### `backstage-cli-module-build package clean`
 
 ```

packages/cli-module-build/src/index.ts

@@ -38,7 +38,8 @@ export default createCliModule({
       description:
         'Bundle a plugin for dynamic loading. Creates a self-contained plugin ' +
         'package that can be deployed and loaded dynamically by a Backstage application. ' +
-        'Supports both backend and frontend plugins.',
+        'Supports both backend and frontend plugins. Experimental.',
+      experimental: true,
       execute: { loader: () => import('./commands/package/bundle') },
     });