Move mouse movement settings to sidebar

[enaboapps]

Closes #864.

Give Mouse movement settings their own destination in the left sidebar, between Scanning and Mobile. Pointer speed and mouse repeat controls move there without changing their shared saved values or behavior. Settings → Controls becomes Settings → Input for the mobile stop-to-click and held-key repeat controls.

• The Mouse page explains that its movement settings also affect Remote, while scanning mode and panel timing remain under Scanning.
• The repeat switch stays visible; movement, acceleration, and scroll intervals sit under Repeat timing.
• Scanning → Mouse points to the sidebar Mouse page for speed and repeat.
• Cursor appearance remains in Settings. No persisted or protocol schemas change.

Validation on Node 24.19.0 and Rust 1.97.1:

• npm run lint, npm test (220 UI tests, 5 Node tests), npm run build pass on the latest head.
• cargo fmt --check, cargo clippy --all-targets -- -D warnings, cargo test (521 unit tests, 1 ignored, 7 integration tests) passed on the initial head; the follow-up changes touch only React markup and a UI test.
• UI tests cover sidebar order and navigation, control placement and accessibility, saved values across pages, and existing settings behavior.
• Built UI head 69911f39923c98f1366b7970ab6d6b3022d36355 as a native Windows ARM64 debug app on the running Windows 11 Parallels VM. Launched it and inspected the Mouse page visually: the sidebar destination, pointer presets, exact speed control, visible repeat switch, and Repeat timing disclosure rendered as expected, with the existing 1350% saved value shown.
• In the native VM app, navigated to Settings → Input and confirmed stop-to-click and held-key repeat controls are present while pointer speed is absent. This is a settings-only move; native switch movement was not retested.
• The first CI run exposed an unrelated focus assertion that ran before React completed its focus restoration effect. Both affected assertions now wait for focus, and the full local frontend suite passes. The final CI run is pending. Independent review of the latest head found no actionable issues.