Fail browsingContext.navigate if navigation is aborted

[sadym-chromium]

Currently, the browsingContext.navigate command's await a navigation succeeds in case of "navigation aborted".

Repro: https://github.com/web-platform-tests/wpt/pull/48751/files
Currently, there is a WPT test test_with_new_navigation_inside_page which is not aligned with the spec.

Spec:

• browsingContext.navigate
• Aawait a navigation:
• Navigate navigable...
• navigate, step 22.3: abort a document and its descendants given navigable's active document.
• Abort a document and its descendants:
• Abort a document
• If document's during-loading navigation ID for WebDriver BiDi is non-null, then:
• Invoke WebDriver BiDi navigation aborted (emits browsingContext.navigationAborted event).
• This case does not fall under "If event received is "navigation failed" return error with error code unknown error"
• "Return success with data body."

Having that, either WPT test or spec should be changed. We propose the latest: change the spec, so that if the navigation is aborted, the command will fail:

If event received is "navigation failed" or "navigation aborted" return error with error code unknown error.

[OrKoN]

Related #112