RangeSelector: Making the maximum and minimum values the same crashes the system

### Describe the bug

The system crashes when the maximum and minimum values are set to the same value

In some cases, Ctrl+Alt+Del may be delayed before the security options appear

### Steps to reproduce

```text
1. Go to the RangeSelector page
2. Make the maximum and minimum values the same via slider (like max=0, min=0)

It may take 0-5 seconds for the system to crash
```

### Expected behavior

The app handles it correctly and does not crash

### Screenshots

### Code Platform

- [ ] UWP
- [x] WinAppSDK / WinUI 3
- [ ] Web Assembly (WASM)
- [ ] Android
- [ ] iOS
- [ ] MacOS
- [ ] Linux / GTK

### Windows Build Number

- [ ] Windows 10 1809 (Build 17763)
- [ ] Windows 10 1903 (Build 18362)
- [ ] Windows 10 1909 (Build 18363)
- [ ] Windows 10 2004 (Build 19041)
- [ ] Windows 10 20H2 (Build 19042)
- [ ] Windows 10 21H1 (Build 19043)
- [ ] Windows 10 21H2 (Build 19044)
- [ ] Windows 10 22H2 (Build 19045)
- [ ] Windows 11 21H2 (Build 22000)
- [ ] Windows 11 22H2 (Build 22621)
- [ ] Windows 11 23H2 (Build 22631)
- [ ] Windows 11 24H2 (Build 26100)
- [x] Windows 11 25H2 (Build 26200)
- [ ] Windows 11 26H1 (Build 28000)
- [ ] Other (specify)

### Other Windows Build number

_No response_

### App minimum and target SDK version

- [ ] Windows 10, version 1809 (Build 17763)
- [ ] Windows 10, version 1903 (Build 18362)
- [ ] Windows 10, version 1909 (Build 18363)
- [ ] Windows 10, version 2004 (Build 19041)
- [ ] Windows 10, version 2104 (Build 20348)
- [ ] Windows 11, version 22H2 (Build 22000)
- [ ] Windows 11, version 24H2 (Build 26100)
- [ ] Windows 11, version 25H2 (Build 26200)
- [ ] Windows 11, version 26H1 (Build 28000)
- [ ] Other (specify)

### Other SDK version

_No response_

### Visual Studio Version

2026

### Visual Studio Build Number

_No response_

### Device form factor

_No response_

### Additional context

Surface Pro 11 (ARM64)

### Help us help you

No, I'm unable to contribute a solution.

Beginne auf der RangeSelector-Seite in der WinAppSDK / WinUI 3-App und reproduziere den Absturz, indem du das Minimum und Maximum des Schiebereglers auf denselben Wert, beispielsweise 0, setzt. Verfolge das Verhalten von RangeSelector bei gleichen Grenzen und stelle sicher, dass die App responsiv bleibt und nicht abstürzt, auch auf der gemeldeten Windows 11 ARM64-Konfiguration.

Vom Indexierungsmodell aus dem Issue-Text verfasst.