fix: allow delayed auto-connect DevTools handshake

[SUSINDRAREDDY]

Summary

• extend the direct DevTools WebSocket verification window used by --auto-connect
• keep the active-port WebSocket path preferred before HTTP discovery
• add a regression test for delayed WebSocket handshakes, matching Chrome remote-debugging permission approval latency

Fixes #1365.

Verification

• cargo test --manifest-path cli/Cargo.toml native::cdp::chrome::tests::
• cargo fmt --manifest-path cli/Cargo.toml -- --check
• cargo clippy --manifest-path cli/Cargo.toml --all-targets -- -D warnings
• git diff --check

[vercel]

@SUSINDRAREDDY is attempting to deploy a commit to the Vercel Labs Team on Vercel.

A member of the Team first needs to authorize it.

[Copilot]

Pull request overview

Extends the WebSocket verification timeout used by --auto-connect from 2 seconds to 30 seconds so users have enough time to approve Chrome's remote-debugging permission prompt (#1365).

Changes:

• Introduce AUTO_CONNECT_WS_VERIFY_TIMEOUT constant (30s) and pass it through to verify_ws_endpoint.
• Make verify_ws_endpoint accept the timeout as a parameter instead of a hardcoded 2s value.
• Add a regression test simulating a delayed (~2.2s) handshake.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.