The tests appear to pass, but there is a new console.error produced in
the browser tests, apparently due to page-with

Upgrade to Jest 28, which is necessary because earlier versions
do not export the `fetch` global (among others). In Jest 28
the system for injecting globals is changed to fix this issue.

See: https://jestjs.io/blog/2022/04/25/jest-28#all-nodejs-globals

Also upgrade related dependencies and update import path
of `AsymmetricMatchers` which was moved in this version.

Starting in Node v18, Node resolves an address (like `localhost`)
by returning IP addresses in the order they are returned from the
OS resolver/DNS. [0] This means that on default-IPv6 systems like
a GitHub Actions runner, the link-local address `::1` is returned
instead of `127.0.0.1`.

Unfortunately this new behavior causes a bug in `@open-draft/test-server`,
which serializes an IPv6 host into an invalid URL, because it
incorrectly does not surround the host with square brackets
like it should (e.g. `http://[::1]:8181`).

Since I could not locate the source of `@open-draft/test-server`
to fix this bug, the work-around is to replace all references
to `localhost` with `127.0.0.1` directly - AFAICT there is no
good reason to test this resolution behavior anyway.

[0] nodejs/node#40537

…0.0.1"

This reverts commit a85c13b.

…/http-server IPv6 behavior

Replace all imports _in test files_ that imported `@open-draft/http-server`
with the `TestHttpServer` shim that applies the bugfix to
serialize IPv6 hosts into valid URLs.

Note this does not replace any imports in `src/`, of which there
are two, but they import `until` from `@open-draft`, and do not
use it for creating any `HttpServer` instance

…ndency

The `page-with` package introduces a transitive dependency on `memfs`,
and specifies a semver range that excludes the latest version of `memfs`
which is compatible with Node v18.

Use the `resolutions` field of `package.json` to force Yarn classic
to install the (currently) latest version of `memfs` regardless of
semver range requested by `page-with`

This fixes at least one bug in `memfs` running in Node v18, which
caused excessive `console.error` spam which rightfully complained
of leaking file descriptors.

For docs on `resolutions` field behavior of Yarn classic, see:
https://classic.yarnpkg.com/en/docs/selective-version-resolutions