test: migrate pages handler validation tests to mocks

[dhananjaypai08]

Refs #2639

Summary

• Move the list_pages handler test and the new_page / navigate_page URL validation tests in tests/tools/pages.test.ts onto createHandlerMocks().
• Assert the list_pages response flags (setIncludePages, setListThirdPartyDeveloperTools, setListWebMcpTools) and that rejected URLs never call context.newPage or page.pptrPage.goto.
• Keep the remaining real-browser tests in this file (page close recovery, extensions, dialogs, chrome://newtab/, focus, isolated contexts).

Test plan

• npm run test tests/tools/pages.test.ts -- --test-name-pattern='list pages$|javascript URL|javascript, data, or vbscript|does not parse|chrome: and chrome-untrusted|chrome-extension: URLs unless'
  • 9/9 passed in ~69ms with PUPPETEER_EXECUTABLE_PATH pointed at a nonexistent binary
• npm run test tests/tools/pages.test.ts
• npm run format

[OrKoN]

Thanks, let's make the following changes:

1. In tests/tools/pages.test.ts (the --no-javascript-evaluation tests for newPage and navigatePage), rebase on main and pass {javascriptEvaluation: false} directly to createHandlerMocks({javascriptEvaluation: false}) instead of parsing CLI flags. Commit #2861 replaced parseArguments with ConfigParser on main, causing a rebase conflict, and passing the option directly to createHandlerMocks avoids manual argument parsing altogether.

2. In tests/tools/pages.test.ts, destructure args directly from createHandlerMocks() across the migrated list_pages, newPage, and navigatePage tests instead of repeatedly calling createMockParsedArguments(). createHandlerMocks() already initializes and returns args with default mock options, making the extra createMockParsedArguments() invocations redundant.