🧹 Refactor endpoint_owner_process_ids for macOS in src/cdp.rs

[undivisible]

🎯 What: Extracted process listing and socket matching logic from endpoint_owner_process_ids for macOS in src/cdp.rs into separate helper functions (list_all_process_ids and process_has_tcp_listen_socket).
💡 Why: The original function was over 100 lines long, making it hard to maintain and read. This refactoring breaks it down into distinct, logical components.
✅ Verification:

1. Ran cargo check --lib continuously during the refactoring process.
2. Verified code style with cargo fmt --all and cargo clippy --all-targets --all-features -- -D warnings.
3. Ran cargo test --lib (bypassing the known local Praefectus state directory is not private environment issue on conformance tests). All tests passed successfully.
   ✨ Result: The endpoint_owner_process_ids function is now under 15 lines of code, highly readable, and delegates complex native OS calls to dedicated, well-named helpers.

---

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

---

Note

Low Risk
macOS-only internal refactor of CDP endpoint ownership probing; behavior should be equivalent and tests still cover live loopback binding.

Overview
On macOS only, the logic that finds which process owns a CDP loopback listen port is restructured without changing the overall security check (verify_endpoint_owner still requires a single matching browser PID).

The monolithic endpoint_owner_process_ids implementation is split into list_all_process_ids (proc_listallpids sizing and buffer fill) and process_has_tcp_listen_socket (per-PID FD scan via proc_pidinfo / proc_pidfdinfo for a localhost TCP LISTEN on the configured port). The top-level function now walks every positive PID and collects owners when the helper returns true.

Socket-matching rules (TCP listen, localhost, port bytes) are the same as before; this is primarily a readability and maintainability change in src/cdp.rs.

^{Reviewed by Cursor Bugbot for commit 01b24d7. 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.