fix(multiple): some experimental components not cleaned up completely

Fixes a few cases where we weren't destroying the MDC foundation in our own components. There's also a case where we were overriding the `ngOnDestroy` from a parent component, but we weren't calling it from the override.

Author: crisbeto

src/material-experimental/mdc-form-field/form-field.ts

@@ -408,6 +408,7 @@ export class MatFormField
   }
 
   ngOnDestroy() {
+    this._foundation.destroy();
     this._destroyed.next();
     this._destroyed.complete();
   }

src/material-experimental/mdc-list/list-option.ts

@@ -201,6 +201,8 @@ export class MatListOption extends MatListItemBase implements ListOption, OnInit
   }
 
   override ngOnDestroy(): void {
+    super.ngOnDestroy();
+
     if (this.selected) {
       // We have to delay this until the next tick in order
       // to avoid changed after checked errors.

src/material-experimental/mdc-list/selection-list.ts

@@ -183,6 +183,7 @@ export class MatSelectionList
   }
 
   override ngOnDestroy() {
+    this._foundation.destroy();
     this._destroyed.next();
     this._destroyed.complete();
     this._isDestroyed = true;

src/material-experimental/mdc-snack-bar/snack-bar-container.ts

@@ -171,6 +171,7 @@ export class MatSnackBarContainer
   /** Makes sure the exit callbacks have been invoked when the element is destroyed. */
   ngOnDestroy() {
     this._mdcFoundation.close();
+    this._mdcFoundation.destroy();
   }
 
   enter() {