fix(multiple): remove workarounds for formControl directive

The formControl directive previously did not mark itself for check, so
several components that work closely with this directive marked for
check on its behalf as a workaround. Now that the directive is fixed we
can remove the workarounds.

src/material/autocomplete/autocomplete-trigger.ts

@@ -462,7 +462,6 @@ export class MatAutocompleteTrigger
   // Implemented as part of ControlValueAccessor.
   setDisabledState(isDisabled: boolean) {
     this._element.nativeElement.disabled = isDisabled;
-    this._changeDetectorRef.markForCheck();
   }
 
   _handleKeydown(event: KeyboardEvent): void {

src/material/chips/chip-grid.ts

@@ -21,7 +21,6 @@ import {
   EventEmitter,
   Input,
   OnDestroy,
-  OnInit,
   Optional,
   Output,
   QueryList,
@@ -91,8 +90,7 @@ export class MatChipGrid
     ControlValueAccessor,
     DoCheck,
     MatFormFieldControl<any>,
-    OnDestroy,
-    OnInit
+    OnDestroy
 {
   /**
    * Implemented as part of MatFormFieldControl.
@@ -280,14 +278,6 @@ export class MatChipGrid
     );
   }
 
-  ngOnInit() {
-    if (this.ngControl) {
-      this.ngControl.control?.events.pipe(takeUntil(this._destroyed)).subscribe(() => {
-        this._changeDetectorRef.markForCheck();
-      });
-    }
-  }
-
   ngAfterContentInit() {
     this.chipBlurChanges.pipe(takeUntil(this._destroyed)).subscribe(() => {
       this._blur();

src/material/radio/radio.ts

@@ -275,7 +275,6 @@ export class MatRadioGroup implements AfterContentInit, OnDestroy, ControlValueA
   _touch() {
     if (this.onTouched) {
       this.onTouched();
-      this._changeDetector.markForCheck();
     }
   }