feat(razer): standard-matrix lighting for the Diamondback Chroma

[ydw1904]

Summary

Adds lighting to the generic RazerHidClient for Chroma-era mice that OpenRazer drives through its older standard-matrix commands (class 0x03). It is gated per product by a new standardMatrixLighting flag, which only the Diamondback Chroma (0x004c) has.

Stacked on #150: the first commit is that PR, so review the second one.

• Codec (src/razer/codec.ts): razerSetStandardEffectCommand covers off, spectrum, wave, static, reactive and breathing random/single/dual on 0x03/0x0a. razerSetBacklightBrightnessCommand, RAZER_BACKLIGHT_BRIGHTNESS_READ and decodeBacklightBrightness cover 0x03/0x03 and 0x03/0x83 on the backlight led (0x05), with the 0-255 level shown as whole percent.
• Driver: readStatus() returns one "Mouse" lighting zone with the brightness the mouse reports (25/50/75/100 offered). setLighting() writes the effect, then writes the brightness only when it changed and confirms it by reading it back. The effect has no read, so it is cached and the card is marked write-only, the same as on the Cobra and Viper Mini.
• App: nothing to wire. The Lighting tab renders from status.lighting and calls setLighting generically. Checked against the app's main (0.22.0) with this branch linked: tsc and all 254 app tests pass, and a preview of this driver's status output renders the card with all eight effects and the brightness row. The app only needs the version bump after a release.

Evidence

OpenRazer driver/razermouse_driver.c (master), USB_DEVICE_ID_RAZER_DIAMONDBACK_CHROMA:

• the probe creates backlight_matrix_effect_{none,static,wave,spectrum,reactive,breath}, backlight_led_brightness, matrix_effect_custom and matrix_custom_frame, with no button or macro attributes
• effects use razer_chroma_standard_matrix_effect_* on transaction id 0xff, and brightness uses razer_chroma_standard_{get,set}_led_brightness(VARSTORE, BACKLIGHT_LED) on 0xff
• payloads and declared data sizes come from razerchromacommon.c and are pinned in protocol.test.ts

Assumptions and unknowns

• Untested on hardware. There is no Synapse capture; the bytes come from OpenRazer. The reporter has the mouse, and the lighting checklist is in docs/razer-testing.md.
• Breathing goes out on 0xff, although OpenRazer lists this model's breathing on 0x3f. That entry sits in the same block as the Cobra, whose breathing answered on its usual id. If breathing alone fails, this is the line to change.
• Wave always runs in direction 0x01, because the card has no direction control.
• Not included: per-LED custom frames, a wave direction option, and the other Chroma-era mice OpenRazer drives the same way (Mamba wired/TE, Orochi Chroma) until someone tests one.
• Whether the effect survives a replug is unknown (checklist step 5).