fix: update target version for ng update steps

Author: geromegrignon

src/app/recommendations.ts

@@ -251,7 +251,7 @@ export const RECOMMENDATIONS: Step[] = [
 
   { possibleIn: 1600, necessaryAsOf: 1600, level: ApplicationComplexity.Basic, step: 'v16 node support', action: 'Make sure that you are using a supported version of node.js before you upgrade your application. Angular v16 supports node.js versions: v16 and v18.' },
   { possibleIn: 1600, necessaryAsOf: 1600, level: ApplicationComplexity.Basic, step: 'v16 ts support', action: 'Make sure that you are using a supported version of TypeScript before you upgrade your application. Angular v16 supports TypeScript version 4.9.3 or later.' },
-  { possibleIn: 1500, necessaryAsOf: 1500, level: ApplicationComplexity.Basic, step: 'v16 ng update', action: 'In the application\'s project directory, run `ng update @angular/core@16 @angular/cli@16` to update your application to Angular v16.' },
+  { possibleIn: 1600, necessaryAsOf: 1600, level: ApplicationComplexity.Basic, step: 'v16 ng update', action: 'In the application\'s project directory, run `ng update @angular/core@16 @angular/cli@16` to update your application to Angular v16.' },
   { possibleIn: 1600, necessaryAsOf: 1600, level: ApplicationComplexity.Basic, step: 'v16 zone.js support', action: 'Make sure that you are using a supported version of Zone.js before you upgrade your application. Angular v16 supports Zone.js version 0.13.x or later.' },
   { possibleIn: 1600, necessaryAsOf: 1600, level: ApplicationComplexity.Advanced, step: 'v16 RouterEvent', action: 'The Event union no longer contains `RouterEvent`, which means that if you\'re using the Event type you may have to change the type definition from `(e: Event)` to `(e: Event|RouterEvent)`'},
   { possibleIn: 1600, necessaryAsOf: 1600, level: ApplicationComplexity.Advanced, step: 'v16 routerEvent prop type', action: 'In addition to `NavigationEnd` the `routerEvent` property now also accepts type `NavigationSkipped`'},
@@ -283,7 +283,7 @@ export const RECOMMENDATIONS: Step[] = [
   { possibleIn: 1700, necessaryAsOf: 1700, level: ApplicationComplexity.Basic, step: 'v17 node support', action: 'Make sure that you are using a supported version of node.js before you upgrade your application. Angular v17 supports node.js versions: v18.13.0 and newer' },
   { possibleIn: 1700, necessaryAsOf: 1700, level: ApplicationComplexity.Basic, step: 'v17 ts support', action: 'Make sure that you are using a supported version of TypeScript before you upgrade your application. Angular v17 supports TypeScript version 5.2 or later.' },
   { possibleIn: 1700, necessaryAsOf: 1700, level: ApplicationComplexity.Basic, step: 'v17 zone.js support', action: 'Make sure that you are using a supported version of Zone.js before you upgrade your application. Angular v16 supports Zone.js version 0.14.x or later.' },
-  { possibleIn: 1500, necessaryAsOf: 1500, level: ApplicationComplexity.Basic, step: 'v17 ng update', action: 'In the application\'s project directory, run `ng update @angular/core@17 @angular/cli@17` to update your application to Angular v17.' },
+  { possibleIn: 1700, necessaryAsOf: 1700, level: ApplicationComplexity.Basic, step: 'v17 ng update', action: 'In the application\'s project directory, run `ng update @angular/core@17 @angular/cli@17` to update your application to Angular v17.' },
   { possibleIn: 1700, necessaryAsOf: 1700, level: ApplicationComplexity.Medium, step: 'v17 style removal', action: 'Angular now automatically removes styles of destroyed components, which may impact your existing apps in cases you rely on leaked styles. To change this update the value of the `REMOVE_STYLES_ON_COMPONENT_DESTROY` provider to `false`.' },
   { possibleIn: 1700, necessaryAsOf: 1700, level: ApplicationComplexity.Basic, step: 'v17 router removals', action: 'Make sure you configure `setupTestingRouter`, `canceledNavigationResolution`, `paramsInheritanceStrategy`, `titleStrategy`, `urlUpdateStrategy`, `urlHandlingStrategy`, and `malformedUriErrorHandler` in `provideRouter` or `RouterModule.forRoot` since these properties are now not part of the `Router`\'s public API' },
   { possibleIn: 1700, necessaryAsOf: 1700, level: ApplicationComplexity.Advanced, step: 'v17 ngDoCheck dynamic components', action: 'For dynamically instantiated components we now execute `ngDoCheck` during change detection if the component is marked as dirty. You may need to update your tests or logic within `ngDoCheck` for dynamically instantiated components.' },