@uppy/companion: migrate from Jest to node:test

[aduh95]

Tests are not passing, I figured I should open it as a draft PR and leave it as it for now, we might want to come back to it at a later time.
The upside of node:test in comparison to Jest is that's it's much simpler, doesn't create its own env (and therefore avoid running into issues specific to the test runner rather than the actual code), and would support whatever Node.js itself support – including ESM packages.

[Murderlon]

I think it's likely that we'll move to Vitest for all tests in the Uppy repo. If that happens, I'd rather have Companion on Vitest too, instead of a different test runner just for Companion.

[aduh95]

I think it's likely that we'll move to Vitest for all tests in the Uppy repo. If that happens, I'd rather have Companion on Vitest too, instead of a different test runner just for Companion.

Note that Companion is running on a different env already (jsdom vs node), so it can't be consistent all the way anyway.

[socket-security]

New, updated, and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Packages	Version	New capabilities	Transitives	Size	Publisher
expect	28.1.3	eval	+28	1.63 MB	simenb
supertest	6.2.4...6.3.3	network	+4/-2	1.29 MB	titanism

🚮 Removed packages: [email protected]