Exclude several Navigation API tests from from Interop 2025

[farre]

Test List

web-platform-tests/wpt-metadata#8228

Rationale

The tests do not test spec due to expecting behavior not present in spec. The ways in which it does this is:

• They expect Promise.all behavior for calling #commit-a-navigate-event[1] when it's specced that #wait-for-all[2] should be used.
• #commit-a-navigate-event[3] falls through after asynchronously calling #resume-applying-the-traverse-history-step, where the same #wait-for-all can finish before the resumption of #apply-the-history-step[5] finishes.

See the discussion in:

• No implementation calls #resume-applying-the-traverse-history-step entirely async whatwg/html#11814
• Navigation API: Inconsistency between spec and tests about WaitForAll whatwg/html#11845

[1] https://html.spec.whatwg.org/#commit-a-navigate-event
[2] https://webidl.spec.whatwg.org/#wait-for-all
[3] https://html.spec.whatwg.org/#navigate-event-firing:resume-applying-the-traverse-history-step
[4] https://html.spec.whatwg.org/#resume-applying-the-traverse-history-step
[5] https://html.spec.whatwg.org/#apply-the-history-step

Rationale

No response

[nairnandu]

@natechapin could you review this test change proposal for Chromium?

[smaug----]

@foolip
(Issues related to Navigation API implementations and tests were discussed at @ TPAC)