PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/angular/angular/blob/main/contributing-docs/commit-message-guidelines.md
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• angular.dev application / infrastructure changes
• Other... Please describe:

What is the current behavior?

If a module imports 2 modules with the same name but one with an alias, the aliased one is not added to the component imports array

e.g. when migrating this component:

import { Component, NgModule } from '@angular/core';
import { AnotherModule } from '../another/another';
import { AnotherModule as LegacyAnotherModule } from '../another/another-legacy';

@Component({
  selector: 'my-comp',
  template: '<another1 /> <another2 />',
  standalone: false
})
export class MyComponent {}

@NgModule({
  imports: [AnotherModule, LegacyAnotherModule],
  declarations: [MyComponent],
  exports: [MyComponent]
})
export class MyModule {}

The component imports array is set to:

imports: [AnotherModule]

Issue Number: #63913

What is the new behavior?

When migrating the example above, the component imports array is set to:

imports: [AnotherModule, LegacyAnotherModule]

Does this PR introduce a breaking change?

• Yes
• No

Other information