feat: report new URL after actions that trigger navigation

[rogeroliveira84]

Summary

• Input tools (click, fill, press_key, hover, drag, type_text, fill_form, click_at) and evaluate_script now append a Page navigated to <url>. line to the response when the action triggers a cross-document navigation.
• WaitForHelper.waitForEventsAfterAction returns {navigated: boolean} instead of void, surfacing the navigation signal that was already being detected internally.
• No change to navigate_page or new_page since they already report the URL explicitly.

Fixes #243

Why

Today, if a click causes a page navigation, the response says "Successfully clicked on the element" with no indication that the page URL changed. The agent has to make an extra list_pages call to discover where it landed. This saves that round-trip for every navigation-triggering action.

Design

The existing waitForNavigationStarted in WaitForHelper already knows whether a cross-document navigation started. We propagate that signal as {navigated: boolean} through the return value of waitForEventsAfterAction → McpPage → ContextPage interface, and let each handler append the URL line when navigated is true.

Same-document (history API) navigations remain filtered out by the existing waitForNavigationStarted logic, matching current behavior. Click-opens-new-tab is a separate concern (#367).

Test plan

• New test: click on a link that causes navigation → response includes Page navigated to <url>.
• New test: click on a button that doesn't navigate → no navigation line in response
• Full test suite (563 tests) passes
• TypeScript typecheck clean
• ESLint + Prettier clean

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[Lightning00Blade]

Thanks for the PR,
there are some comments that would need to be address before we can merge.

[masamaru0513]

Hi @rogeroliveira84, thanks for the original PR and the groundwork here! I noticed the review feedback from @Lightning00Blade hadn't been addressed yet, so I went ahead and opened #1954 incorporating those suggestions (navigatedToUrl naming, shared helper in WaitForHelper.ts, etc.).

[rogeroliveira84]

Hi @Lightning00Blade I have on going work for that was planing to push later on, but once I do you can also check comment on it and see how it goes... cheers!

[rogeroliveira84]

Hi @Lightning00Blade I pushed changes, could review pls. Thanks.