Numpad doesn't work after startup until caps lock setting is changed

### What Happened?

I cannot use my numpad after boot on Wayland. Changing the numlock setting with either my keyboard or the onscreen keyboard does not enable it. It only works after changing the caps lock setting to anything once during the session.

### Steps to Reproduce

1. Boot OS
2. Try to type with numpad (doesn't work)
3. Go to Settings --> Keyboard
4. Change the caps lock setting to anything
5. Try typing with numpad again (it now works until reboot)

### Expected Behavior

Numpad should work without having to arbitrarily change the caps lock setting.

### OS Version

8.x (Circe)

### OS Architecture

amd64 (on most hardwares)

### Session Type

Secure Session (Wayland, This is the default)

### Software Version

Latest release (I have run all updates)

### Log Output

```shell

```

### Hardware Info

Keyboard: Preonic V3
CPU: AMD Ryzen 9 5950X 16-core
GPU: AMD Radeon RX 9070 XT

Start by reproducing the startup sequence in the Wayland Secure Session and compare numpad behavior before and after changing the caps lock setting in Settings → Keyboard. Trace the keyboard settings path to identify the state update associated with enabling numpad; done means numpad works immediately after boot without changing caps lock.

Written by the indexing model from the issue text.