[Bug]: Angular-Vite automigration leaves `@storybook/angular` imports untransformed in files it cannot attribute to a Storybook instance

[Sidnioulz]

Describe the bug

When automigrating an Angular 21 project to the Angular-Vite builder, several files retaining @storybook/angular imports are not rewritten. In the Bitwarden clients repo, untransformed files were found under libs/, apps/, .github/, .claude/ and bitwarden_license/.

This is a known architectural limitation: the automigration intentionally only transforms files it can safely attribute to a specific Storybook instance (stories, main config, preview config), to avoid breaking other Storybook instances in a monorepo.

Expected behavior / agreed mitigation

A post-migration scan that detects remaining untransformed import patterns and warns the user to apply them manually — ideally also telling them what to replace them with. Implemented in #35414.

Reproduction link

https://github.com/bitwarden/clients

Reproduction steps

1. Take an Angular 21 monorepo with @storybook/angular imports spread across many packages (e.g. Bitwarden clients).
2. Run the Angular → Angular-Vite automigration (QA task Angular: Introduce @storybook/angular-vite package #34202).
3. Files that cannot be attributed to the migrated Storybook instance keep their @storybook/angular imports, with no warning.

System

Storybook: 10.5.0-alpha.11
Project: Bitwarden clients (Angular 21)

Additional context

Found during internal 10.5 QA.