init url module

[imaitland]

Issue # (if available)

https://github.com/awslabs/llrt/issues/214

Description of changes

Adopt WHATWG URL Spec for ESM import syntax: https://nodejs.org/api/url.html#new-urlinput-base

The URL constructor is accessible as a property on the global object. It can also be imported from the built-in url module

import { URL, URLSearchParams } from "url";

Also noticed there was a bug in URL.canParse() and fixed it.

Caveats

Original ticket: https://github.com/awslabs/llrt/issues/195 requested URL.parse however this has been deprecated, https://nodejs.org/api/url.html#urlparseurlstring-parsequerystring-slashesdenotehost,

url.parse() uses a lenient, non-standard algorithm for parsing URL strings. It is prone to security issues such as host name spoofing and incorrect handling of usernames and passwords. Do not use with untrusted input. CVEs are not issued for url.parse() vulnerabilities. Use the WHATWG URL API instead.

though it does seem to be used fairly widely, a succinct description of the situation is here: https://github.com/nodejs/node/issues/12682#issuecomment-736510378

along with discussion within WHATWG here: https://github.com/whatwg/url/issues/531

Future work

• [ ] https://github.com/awslabs/llrt/issues/303 Implement and expose in the url module helper functions: https://nodejs.org/api/url.html#urldomaintoasciidomain https://nodejs.org/api/url.html#urldomaintounicodedomain https://nodejs.org/api/url.html#urlfileurltopathurl https://nodejs.org/api/url.html#urlpathtofileurlpath https://nodejs.org/api/url.html#urlurltohttpoptionsurl
• [ ] Implement URLSearchParams.sort() and URLSearchParams.keys()
• [ ] Figure out if URL.toJSON() is needed and implement if it is.

Checklist

• [x] Created unit tests in tests/unit and/or in Rust for my feature if needed
• [x] Ran make fix to format JS and apply Clippy auto fixes
• [x] Made sure my code didn't add any additional warnings: make check
• [x] Updated documentation if needed (API.md/README.md/Other)

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.