downgrade jsdom to avoid nwsapi

[mbostock]

Fixes #1330. Supersedes #1331.

[mbostock]

It’d probably be useful for us to run yarn upgrade and make sure we’re also testing against the latest dependencies… We were still running against nwsapi 2.2.7 which is why we didn’t notice the problem.

[Fil]

LGTM with a caveat: "^23.0.0" accepts both [email protected] and [email protected], which means we don't guarantee which CSS selector engine is used. To be clear, 23.2.0 is OK, but 23.1.0 is broken (tested broken) — and any previous version is probably broken too because they all use nwsapi.

So I think we'd be better off being explicit about "jsdom": "=23.2.0"?

[mbostock]

I think we should do ^23.2.0 since that’s pretty standard and if they were to do a patch on 23.x it seems like they would keep the same non-broken selectors implementation.