fix(chrome): sort Playwright Chromium by revision, not lexically

[nsiddharth]

What

_candidate_chrome_paths sorts Playwright's chromium-* browser
directories lexicographically:

paths.extend(sorted(glob.glob(str(cache_dir / rel_glob)), reverse=True))

The comment promises "Newest chromium-NNNN first," but a string sort
breaks that contract once the revision crosses the 3→4 digit boundary:
"chromium-999" ranks above "chromium-1187". Since find_chrome()
returns the first valid match, the resolver then silently selects an
older Chromium than the one the user just installed.

This triggers whenever two or more Playwright Chromium revisions are
cached and straddle that boundary — a normal state after playwright install upgrades, which leave older revisions in place.

Fix

Sort by the integer revision parsed from chromium-<n> instead of by
string. Paths without a recognizable revision sort last (-1) rather
than raising.

Test

Adds test_playwright_chromium_sorted_by_revision_not_lexically, which
feeds chromium-999, chromium-1187, chromium-1208 and asserts the
candidate list is newest-first. It fails on the old lexicographic sort
(chromium-999 landed first) and passes with this change. The existing
chrome-path tests are unaffected (6 passed).

[vercel]

@nsiddharth is attempting to deploy a commit to the andylizf's projects Team on Vercel.

A member of the Team first needs to authorize it.

[andylizf]

The sort fix is correct — lexicographic sort breaks when Playwright revisions cross the 3→4 digit boundary (e.g. chromium-999 > chromium-1208). The _playwright_revision helper + test look good.

However, like #73, this PR is based on an older main and carries a large number of unrelated regressions (removes --cdp-url, --user-data-dir isolation, pre-commit hooks, reverts production URLs, etc.).

Could you rebase onto the latest origin/main so the PR contains only the chrome.py sort fix + test?

git fetch upstream main
git rebase upstream/main
git push --force-with-lease

[nsiddharth]

Thanks for the review! Rebased onto the latest main (8d5c607) — the branch now carries only the two-file change (chrome.py sort fix + the test_chrome_paths.py test), so it sits cleanly on top of #75/#65/#49/#66/#76. Tests pass (6 passed) and ruff check / ruff format --check are clean against the new pre-commit hook.