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

Start with the reproduction in src/example/chips-input-example.html from the linked StackBlitz and compare the disabled MatChipInput with the disabled MatInput. Verify the MatFormField wrapper behavior in both cases and confirm that the completed change makes the wrapper receive mat-form-field-disabled for a disabled chip input.

Written by the indexing model from the issue text.