fix: add missing backstage.features filed for standard Module federation assets

[davidfestal]

Summary

Implements RHIDP-15376.

Upstream Backstage's backstage-cli pack now populates backstage.features in package.json by analyzing each entry point's default export $$type via ts-morph. Since rhdh-cli's forked productionPack predates that addition, this PR adds the same detection as a separate step during frontend dynamic plugin export.

When --generate-module-federation-assets is enabled (the default), the export command now:

• Creates a ts-morph project and reads the package's entry points
• Detects the Backstage feature type for each entry point (e.g. @backstage/FrontendPlugin)
• Writes the detected features into backstage.features in the output package.json

Changes

• New: src/commands/export-dynamic-plugin/features.ts — detectBackstageFeatures() utility mirroring upstream's detection logic
• Modified: src/commands/export-dynamic-plugin/frontend.ts — integrates feature detection and injects results via the after callback of customizeForDynamicUse()
• Modified: scripts/backstage-types-config.json — added type extraction config for typeDistProject and entryPoints modules
• Regenerated: src/generated/backstage-cli-types.d.ts — now includes type declarations for the new internal modules
• Modified: package.json — added ts-morph as a peer dependency (provided transitively by @backstage/cli-module-build)
• Modified: E2E tests — added assertions verifying backstage.features is populated for frontend plugins

Test plan

• Manual verification: rhdh-cli plugin export-dynamic on a frontend plugin produces backstage.features with correct feature types
• E2E tests pass with new backstage.features assertions
• yarn tsc passes

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud