bug(mat-slider): Incorrect slider thumb position when changing min/ max and form value

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

A range slider is bound to a reactive form using `formControlName`; min/ max properties are also bound.
After programmatically updating min/ max variables and calling `setValue` to update the form values, observed behaviour is that range slider thumbs don't match the form values. Expected behaviour is that thumb positions match the calls to `setValue`.

https://github.com/user-attachments/assets/3bb7de78-5d05-436d-90ac-f1288fac8a32

### Reproduction

StackBlitz link: https://stackblitz.com/edit/components-issue-starter-xwmbwzkn?file=src%2Fmain.ts
Steps to reproduce:
1. Select Category A (this sets ranges to be [10, 20] + [20, 30], and absolute min/ max to be [10, 30])
2. Select Category B (this sets ranges to be [5, 15] + [15, 25], and absolute min/ max to be [5, 25])
3. Hover over 1st slider's thumbs

### Expected Behavior

Expected slider 1's thumbs to be at [5, 15] (to match form values after having called `setValue`)

### Actual Behavior

Observed slider 1's thumbs to be at [10, 15] (which doesn't match form values)

### Environment

- Angular: 20.3.15
- CDK/Material: 20.2.14
- Browser(s): Chrome Version 143.0.7499.41 (Official Build) (64-bit)
- Operating System (e.g. Windows, macOS, Ubuntu): Windows 11

Beginne mit der StackBlitz-Reproduktion in src/main.ts und reproduziere die Kategorieänderungen mit dem reactive form, gebundenen min/max-Werten und mat-slider. Untersuche, wie der Slider seine Thumbs aktualisiert, nachdem sich min/max und setValue geändert haben. Fertig ist die Aufgabe, wenn Slider 1 Thumbs bei [5, 15] anzeigt, die den Formularwerten nach der Auswahl von Category B entsprechen.

Vom Indexierungsmodell aus dem Issue-Text verfasst.