fix(@angular/cli): propagate update's force option to package managers

When the CLI update command's `--force` option is used, the underlying package manager will also be executed with its force option. This behavior is especially important with the advent of npm 7 which will fail installation if any peer dependency version ranges are mismatched.

packages/angular/cli/commands/update-impl.ts

@@ -66,10 +66,11 @@ export class UpdateCommand extends Command<UpdateCommandSchema> {
  private workflow!: NodeWorkflow;
  private packageManager = PackageManager.Npm;
 
- async initialize() {
+ async initialize(options: UpdateCommandSchema & Arguments) {
  this.packageManager = await getPackageManager(this.context.root);
  this.workflow = new NodeWorkflow(this.context.root, {
  packageManager: this.packageManager,
+ packageManagerForce: options.force,
  // __dirname -> favor @schematics/update from this package
  // Otherwise, use packages from the active workspace (migrations)
  resolvePaths: [__dirname, this.context.root],

packages/angular/cli/commands/update.json

@@ -28,7 +28,7 @@
  }
  },
  "force": {
- "description": "If false, will error out if installed packages are incompatible with the update.",
+ "description": "Ignore peer dependency version mismatches. Passes the `--force` flag to the package manager when installing packages.",
  "default": false,
  "type": "boolean"
  },