`navigation-api/ordering-and-transition/currententrychange-before-popstate-intercept.html` asserts the wrong thing

[noamr]

It assumes that popstate is called before the finished promise, however this is not the case.
Specifically https://html.spec.whatwg.org/multipage/nav-history-apis.html#commit-a-navigate-event step 7.4

This test assumes that the internal Resume applying the traverse history step is called synchronously, while in fact it is queued.

This test also conflicts with an older test navigation-api/navigate-event/intercept-popstate-no-handler.html.
Since currententrychange-before-popstate-intercept.html was added by webkit and passes only there, andnavigation-api/navigate-event/intercept-popstate-no-handler.html fails in webkit and passes in Chromium/Gecko, I suspect that this test is evidence that something is wrong in the webkit implementation.

Suggesting to remove this test for now and let webkit investigate failure of navigation-api/navigate-event/intercept-popstate-no-handler.html

[noamr]

cc @nt1m (who submitted the test) and @farre to make sure I'm not smoking crack here.

[yulunwu2]

LGTM webkit side

[nt1m]

@natechapin originally wrote this test fwiw