fix(pulsar): report shared 8K receiver rates and unknown polling

[DEERSTUDIO101]

The XS-1 driver currently caps every connection at 1000 Hz, including the 3710:5403 shared 8K receiver reported with the X2A v3. It also substitutes 1000 Hz when the polling query fails or returns an unknown code. This makes a missing read look like a confirmed setting.

Advertise 125 through 8000 Hz for the shared receiver and keep the existing wired/1K list for other IDs. Return the shared unavailable-rate sentinel (pollingRateHz: 0) for failed, unknown or out-of-range replies. Keep polling read-only and explicitly describe its readout as unverified. Name wired 3404 as X2A v3 and shared 5403 as the receiver, without inferring its paired mouse. No Bridge or polling-write changes are included.

The original wired support/interface-selection fix was already merged in #144. docs/pulsar-x2a-v3-testing.md records the remaining hardware checks, descriptor-printing snippet and vendor reference. The existing polling decoding table is unchanged; actual query packets correlated with vendor-selected rates are still needed to verify it.

Validation:

• Strict TypeScript build and npm package generation passed.
• All 36 Pulsar tests passed, covering 2K/4K/8K reports, missing/unknown reads, wired naming and DPI/debounce/processing read-back on both ticket PIDs.
• OpenMouse with the locally packed library passed its build, 294 tests and bundle-size check.
• This scoped run does not claim the complete protocol suite passed; the earlier Windows full-suite run had unrelated Corsair locale assertions and an unfinished exhaustive registry probe.
• Hardware verification remains pending.

Companion panel change: OpenMouse-Project/openmouse#693. It handles the unavailable-rate display and button selection and can merge independently of the driver release.

[github-actions]

🎉 This PR is included in version 0.30.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀