Fix silly npm warnings

[BrennanConroy]

Fixes #10251

@anurse Who does dependency update things now? (This is test only)

[analogrelay]

@anurse Who does dependency update things now? (This is test only)

The formal "compliance" stuff is automated in our build through the Component Governance tools. I think @Pilchie should be notified though, just as @Eilon was in the past despite the automatic stuff.

In this case, the dependency is being updated in order to fix NPM warnings during installation (see linked issue) and is used only in test code. I approve ✔️ of this update.

[analogrelay]

Looks like the ts-jest update barfed on the lock file but c'est la vie.

[BrennanConroy]

Also looks like I forgot to run tests locally, and the update broke some stuff

[Eilon]

Yup, please let @Pilchie know about significant OSS updates. For me the most important ones were ones that affect the shipping product (even minor updates). For test/build-only assets I mostly cared about significant changes (e.g. new dependency).

[BrennanConroy]

ts-jest changed something with how they compiled files which made the types now actually needed, so had to add a new config file to have the correct typeRoots and use that for FunctionalTests

[halter73]

👍

[BrennanConroy]

🆙 📅

[halter73]

Still approved.