bug(MatChipList): chip list disabled should respect each chip item disabled state

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

Chiplist [disabled] toggling from disable to enable doesn't respect each chip item [disabled] state. Chip items, which are actually disabled become visually enabled.

### Reproduction

StackBlitz link: https://stackblitz.com/edit/vdefsz?file=src%2Fexample%2Fchips-input-example.html,src%2Fexample%2Fchips-input-example.ts

Steps to reproduce:
1. The chip item is disabled and has properly disabled styles in initialization
2. Click 'Disable chiplist'
3. Click 'Enable chiplist'

### Expected Behavior

The chip item is visually disabled

### Actual Behavior

The chip item ignores its disabled state and looks like enabled

### Environment

- Angular: 16.2.9
- CDK/Material: 16.2.9
- Browser(s): Google Chrome, Version 118.0.5993.88 (Official Build) (64-bit)
- Operating System (e.g. Windows, macOS, Ubuntu): Windows 10

Use the linked StackBlitz reproduction and start with src/example/chips-input-example.html and src/example/chips-input-example.ts. Reproduce the disable/enable sequence, then trace the MatChipList state handling; done means individually disabled chips retain their disabled appearance after the chip list is re-enabled.

Written by the indexing model from the issue text.