Add multi-waypoint mouse gestures (move/drag through a polyline)

[JE-Chen]

Summary

Round-11, automation-core (per the "focus on automation" steer). humanize.humanized_path and tween_drag only interpolate a single start→end hop. Real gestures — signatures, marquee/rubber-band selects, dragging through several drop targets, shape gestures — need an arbitrary chain of waypoints with the button optionally held down across the whole path.

Layers

• Headless core: je_auto_control/utils/mouse_path/mouse_path.py — plan_path (pure eased point math, reusing tween_drag's named easings, junctions de-duplicated), move_along_path, drag_path (press-first/release-last), path_easings. Dispatch via an injectable sink (mirrors tween_drag); no PySide6.
• Facade: all 4 re-exported + __all__.
• Executor: AC_move_along_path, AC_drag_path (JSON waypoints + easing/per_segment_steps/button).
• MCP: ac_move_along_path / ac_drag_path (SIDE_EFFECT_ONLY).
• Script Builder: two CommandSpecs under Mouse.

Tests / docs

• test/unit_test/headless/test_mouse_path_batch.py — 9 headless tests (junction de-dup, single/empty, move-only events, drag press-first/release-last, empty no-op, easing changes mid-path, JSON coercion + wiring + facade). Dispatch tested via injected sink (no real input).
• EN/Zh feature docs v116_features_doc.rst + toctrees; 3 WHATS_NEW changelog entries.

Note: Codacy may show action_required purely from its coverage gate (issues=0); SonarCloud + all GitHub Actions are the substantive gates.

[codacy-production]

Not up to standards ⛔

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud