🧹 Refactor native_click function by extracting platform logic

[undivisible]

🎯 What: Extracted the macOS and Windows specific logic from the native_click function into separate helper functions (native_click_macos and native_click_windows).
💡 Why: The original native_click function was over 100 lines long and hard to read. By extracting the large platform-specific blocks into helper functions, the main dispatcher function is now concise and much easier to maintain, while keeping platform logic nicely encapsulated.
✅ Verification: Verified by running cargo check, cargo clippy, and cargo test --lib. All tests pass successfully, and no functionality was altered since the exact logic was simply moved into functions.
✨ Result: Improved codebase readability and maintainability for the platform native click handling.

---

PR created automatically by Jules for task 11112059905367842859 started by @undivisible

---

Note

Low Risk
Pure structural refactor with no intended logic changes; risk is limited to accidental copy/paste errors in low-level input code.

Overview
Refactors native_click in src/lib.rs by moving unchanged macOS and Windows implementations into native_click_macos and native_click_windows, leaving the dispatcher as thin cfg-based delegates (Linux still routes to linux_input::native_click).

Behavior should be identical: Windows still moves the cursor with SetCursorPos and synthesizes down/up via SendInput; macOS still requires accessibility permission and posts CG mouse events through the existing helpers.

^{Reviewed by Cursor Bugbot for commit c02f520. Configure here.}

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.