bug(datepicker): Date range picker emit repeated events after the first date is selected

### 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 date range picker is opened and the start date is selected, two consecutive `valueChanges` event are triggered, and after the end date is selected the final event is triggered, in total 3 events happens instead of only two.

### Reproduction

StackBlitz link: https://stackblitz.com/edit/shrtut?
Steps to reproduce:
1. Click on the `mat-datepicker-toggle` button.
2. Select a start date like: 6/18/2023
3. Notice on the _Changes_ section below that two events were triggered.
4. Select the end date: 6/24/2023.
5. A final event in logged on the _Changes_ section.

### Expected Behavior

After selecting the first date only a single `valueChanges` event should be triggered.

The expected behavior is show on the _Workaround Changes_ section where a `debounceTime(0)` is forced in order to remove the spurious repeated event.

### Actual Behavior

Two events are triggered after selecting the start date

### Environment

- Angular: 16.1.1
- CDK/Material: 16.1.1
- Browser(s): Firefox, Chrome.
- Operating System: Linux (Fedora)

Beginne mit der verlinkten StackBlitz-Reproduktion und dem Angular Material date range picker-Ablauf mit mat-datepicker-toggle und valueChanges. Reproduziere im Abschnitt Changes die Auswahl von 6/18/2023 und anschließend 6/24/2023 und vergleiche sie dann mit der debounceTime(0)-Umgehungslösung. Fertig bedeutet: ein valueChanges-Ereignis nach dem Startdatum und eines nach dem Enddatum.

Vom Indexierungsmodell aus dem Issue-Text verfasst.