script: Fix assertion failure when stringifying cross-origin location object

[thebabalola]

This fixes the assertion failure (!JS_IsExceptionPending(*cx)) that happens when console.log() is called on a cross-origin location object (e.g. console.log(frame.contentWindow.location)).

The problem was that maybe_stringify_dom_object calls ToString on cross-origin objects, which throws a JS exception via the DissimilarOriginLocation stringifier. That exception was never cleared, so subsequent JS API calls would hit the assertion.

The fix refactors console_argument_from_handle_value using an inner/outer function pattern based on @jdm's suggestion:

• The inner function returns Result<ConsoleArgument, ()> and returns Err(()) when console_object_from_handle_value returns None for an object, instead of falling through to stringify_handle_value which could trigger the same crash
• The outer function catches the Err, reports any pending JS exception via report_pending_exception, and returns a fallback ConsoleArgument

Fixes #43530

---

• ./mach build -d does not report any errors
• ./mach fmt produces no changes
• There are tests for these changes

[jdm]

This looks good! Can you write a test that uses https://github.com/web-platform-tests/wpt/blob/0f8fc11ddab5f0462806006b46e3b230f6e8a8d0/cors/preflight-failure.htm#L19 to create the cross-origin iframe? We can use a crash test for that, and it can go in tests/wpt/tests/html/browsers/history/the-location-interface

[jdm]

Excellent!

[servo-wpt-sync]

🤖 Opened new upstream WPT pull request (web-platform-tests/wpt#58948) with upstreamable changes.

[thebabalola]

Excellent!

appreciate the review.... would be waiting for CI to finish : )

[jdm]

Hmm, we will need to add the test path to

servo/tests/wpt/tests/lint.ignore

Line 132 in 78ffbe8

# Intentional use of console.*

to avoid one lint failure, then run ./mach update-manifest to fix the rest.

[servo-wpt-sync]

📝 Transplanted new upstreamable changes to existing upstream WPT pull request (web-platform-tests/wpt#58948).

[jdm]

You will need to rebase to the latest changes in main and fix the conflict.

[servo-wpt-sync]

📝 Transplanted new upstreamable changes to existing upstream WPT pull request (web-platform-tests/wpt#58948).

[thebabalola]

with CI checks passing.... this should be ready to be merged...