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.

Commencez par reproduire le StackBlitz lié avec les vérifications strictes des templates activées, en vous concentrant sur les entrées de couleur de mat-button et mat-checkbox. Examinez la manière dont ces entrées sont déclarées dans les composants concernés ; le travail est terminé lorsque les valeurs non valides, telles que les nombres, échouent à la compilation avec une erreur de type incorrect.

Rédigé par le modèle d'indexation à partir du texte de l'issue.