bug(mat-select): wrong initial values when using async object property

### Is this a regression?

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

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

14.2.12

### Description

Hey everyone, if I try to access a property of an object loaded with the async pipe it appears to be empty until I click inside the mat-select element.

It's hard to explain so there's a stackblitz to show the issue.

### Reproduction

https://stackblitz.com/edit/rjpwlz?file=src%2Fexample%2Fselect-no-ripple-example.html

### Expected Behavior

The first mat-select in the example should initially display "2"

### Actual Behavior

The first mat-select seems empty until you click on it

### Environment

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

Comienza con la reproducción vinculada de StackBlitz y verifica el comportamiento usando Angular 16.0.4 con CDK/Material 16.0.3. Compara el renderizado inicial del primer mat-select con el comportamiento anterior de 14.2.12, y considera el issue terminado cuando la propiedad asíncrona del objeto muestre inicialmente "2" sin hacer clic en el select.

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