bug(MatChipInput): MatChipInput does not set `mat-form-field-disabled` on MatFormField wrapper when being disabled

### 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

When a MatChipInput is disabled, it does not set `mat-form-field-disabled` CSS class on its MatFormField wrapper like it does for MatInput.

### Reproduction

StackBlitz link: https://stackblitz.com/edit/xcgzeewq?file=src%2Fexample%2Fchips-input-example.html
Steps to reproduce:
1. There are one disabled MatChipInput and one disabled MatInput in the example
2. The form field wrapper of the MatInput has `mat-form-field-disabled` CSS class, while the form field wrapper of the MatChipInput does not

### Expected Behavior

Both of the form field should set `mat-form-field-disabled` CSS class as the input is disabled.

### Actual Behavior

The form field wrapper of the MatInput has `mat-form-field-disabled` CSS class, while the form field wrapper of the MatChipInput does not

### Environment

- Angular:
- CDK/Material:
- Browser(s): Chrome
- Operating System (e.g. Windows, macOS, Ubuntu): macOS

Comienza con la reproducción en src/example/chips-input-example.html del StackBlitz enlazado y compara el MatChipInput deshabilitado con el MatInput deshabilitado. Verifica el comportamiento del wrapper de MatFormField en ambos casos y confirma que el cambio completado hace que el wrapper reciba mat-form-field-disabled para un chip input deshabilitado.

Escrito por el modelo de indexación a partir del texto del issue.