feat(core): add TS migration

[filipesilva]

Blocked on #32946

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/angular/angular/blob/master/CONTRIBUTING.md#commit
• 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.io application / infrastructure changes
• Other... Please describe:

What is the current behavior?

Issue Number: N/A

What is the new behavior?

Does this PR introduce a breaking change?

• Yes
• No

Other information

[mary-poppins]

You can preview 271ee0f at https://pr33250-271ee0f.ngbuilds.io/.

[devversion]

LGTM schematic code-wise. What's the plan for these type of migrations in the future?

On the angular/components side we have this problem that we need to keep migrations forever in our release package due to the way ng update works (i.e. it installs the latest version and runs migrations for older versions). We are planning on talking about this at some point with the tooling team since we do not want to store all migration code for old versions in our release output (it will blow-up over time).

Same would apply here. I'm just trying to raise awareness as I think that it's not ideal to keep migrations forever in the code-base, plus not all developers use the CLI and we will unnecessarily bloat the @angular/core package for them (worst case slowing down install if we add more over time). Weren't these type of migrations part of the CLI in the past?

[IgorMinar]

This migration has two distinct parts:

• typescript update
• @types/node update

the first one should not be necessary because @angular/core depends on the new version of typescript and ng-update will update the project's typescript version to match that.

the second update of @types/node is not relevant for @angular/core. That dependency is introduced into CLI projects by the CLI scaffolding so that we can write e2e tests in typescript - these tests run in node, hence the need for these typings.

I propose that we remove the migration for the typescript update and move the migration for @types/node into CLI rather than @angular/core.

[filipesilva]

Moving to CLI.

@devversion I am not aware of what that part of the ng update design is. @clydin might know.

[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.}