bug(all): "color" input is not typechecked

### Is this a regression?

- [ ] Yes, this behavior used to work in the previous version

### The previous version in which this bug was not present was

_No response_

### Description

The `color` input of multiple components is not typechecked. It accepts arbitrary strings or even non-string values.

The previous bug report was closed without an action: https://github.com/angular/components/issues/24089

### Reproduction

https://stackblitz.com/edit/urch5g?file=src%2Fexample%2Fbutton-overview-example.html

Note that strict template checks are enabled. If you try to pass an incorrect value (e.g. a number) to the `indeterminate` input of the `mat-checkbox`, the compilation will fail, as expected.

### Expected Behavior

Compilation fails, error message says the value for the `color` input is of incorrect type

### Actual Behavior

The stackblitz example compiles and runs well, despite bogus color values passed to `mat-button` and `mat-checkbox`.

### Environment

The stackblitz above is latest angular - 16 (forked off an example in the Material docs). But it's observed in Angular 15 (various minor versions), and earlier.

Inizia riproducendo lo StackBlitz collegato con i controlli rigorosi dei template abilitati, concentrandoti sugli input del colore di mat-button e mat-checkbox. Esamina come sono dichiarati questi input nei componenti interessati; il lavoro è completato quando i valori non validi, come i numeri, non superano la compilazione e producono un errore di tipo non corretto.

Scritto dal modello di indicizzazione a partire dal testo della issue.