bug(migration): after ng update some Legacy imports are broken

[Marax]

Is this a regression?

• Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was

No response

Description

I've updated angular from version 14 to 15.

There was lot of changes to the imports, but there are two which failed to update correctly:
import {MatDialog} from '@angular/material/dialog';
changed to:
import {MMatLegacyDialog as MatDialog from '@@angular/material/legacy-dialog;
(double MM missing } after MatDialog and missing ' at the end.

and also this
import {FloatLabelType} from '@angular/material/form-field';
to this
import {LegacyFloatLabelType} from '@angular/material/legacy-form-field';
missin as FloatLabelType

For the second one I think problem could be that here

components/src/material/schematics/ng-update/migrations/legacy-components-v15/constants.ts

Line 65 in 4573263

{old: 'LegacyFloatLabelType', new: 'LegacyFloatLabelType'},

both old/new lines are with Legacy prefix

Reproduction

Steps to reproduce:

1. Have angular 14 with file containing
   import {FloatLabelType} from '@angular/material/form-field';
   import {MatDialog} from '@angular/material/dialog';
   imports
2. run ng update @angular/material@15
3. see broken imports

Expected Behavior

Imports should be correctly migrated.

Actual Behavior

Imports are broken as mentioned above.

Environment

• Angular: 14 to 15
• CDK/Material: 15
• Browser(s): N/A
• Operating System (e.g. Windows, macOS, Ubuntu): Windows

[mmalerba]

I just tested this out and I was not able to reproduce the malformed dialog import, but it does fail to migrate FloatLabelType

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}