test, url: update WHATWG URL parser to align with latest spec

[F3n67u]

The PR:

1. update WPT test for url and resource to latest commit: automated by git node wpt
2. remove test-whatwg-url-constructor.js, test-whatwg-url-origin.js, and test-whatwg-url-setters.js because they are now .any.js in the WPT upstream and covered by wpt test
3. add isShadowRealm to global.GLOBAL to avoid wpt test crash: without this property test will fail with global.GLOBAL.isShadowRealm is not a function see https://github.com/web-platform-tests/wpt/blob/master/resources/testharness.js#L544
4. update WHATWG URL parser to align with latest spec
   • Reject non-IPv4 hostnames that end in numbers(Reject non-IPv4 hostnames that end in numbers. whatwg/url#619)
   • Split forbidden host/domain code points, and add all C0 controls and add U+007F to the latter(Split forbidden host/domain code points, and add all C0 controls and add U+007F to the latter whatwg/url#685)

Fix #42920
Fix #41717
Fix #42914: this issue is marked closed by #42915, but #42915 is reverted by #42940, so this issue is still not fixed

[Trott]

@nodejs/url @nodejs/testing

[F3n67u]

This pr got two approvals so I think it is author ready and add the author-ready label.

[F3n67u]

Could you help to rerun just the failed ci? I am tired to rerun Jenkins ci in fresh.

[aduh95]

This pr got two approvals so I think it is author ready and add the author-ready label.

Adding author ready PRs that have at least one approval, no pending requests for changes, and a CI started. is definitely the right thing to do here, FYI I try to make a tour of all author ready PRs that have at least one approval, no pending requests for changes, and a CI started. PRs every once in a while to re-run CI / land them / comment if there are conflicts / genuine CI failures – and I encourage any collaborator to do the same. I wish I could walk through all the PRs that have been open for a while, that's a lot of work, it would be extra nice to have a triagger day where everyone gets assigned one long-open PR/issue and make sure it's addressed.

I am tired to rerun Jenkins ci in fresh.

I understand the frustration, spawning fresh CI is really not a good solution, pinging as you did is a much better solution indeed.

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/45001/

[F3n67u]

wow, CI is green now. could you please land this pr?

[RaisinTen]

wow, CI is green now. could you please land this pr?

@F3n67u I think you'll be able to land this one yourself by applying the commit-queue label + (commit-queue-rebase if you want to land the PR as several commits / commit-queue-squash if you want to squash all the commits into the first commit while landing) ;)

[aduh95]

Landed in 2dccda2

[F3n67u]

Landed in 2dccda2

@aduh95 many thanks.

[F3n67u]

wow, CI is green now. could you please land this pr?

@F3n67u I think you'll be able to land this one yourself by applying the commit-queue label + (commit-queue-rebase if you want to land the PR as several commits / commit-queue-squash if you want to squash all the commits into the first commit while landing) ;)

Thanks. I will try next time.