JSDOM errors are ignored during test-unit runs

[goodov]

While working on Teamcity jest reporting integration I've noticed that JSDOM errors are outputted into stdout, but do not trigger test failures. This does not look right as the test output does contain a clear error, but it's not bound to any test.

 $ cross-env NODE_OPTIONS=--no-experimental-fetch jest -t --verbose ./components/brave_wallet_ui/common/hooks/use-password-attempts.test.tsx
Error: Not implemented: window.alert
    at module.exports (D:\brave\3\src\brave\node_modules\jsdom\lib\jsdom\browser\not-implemented.js:9:17)
    at D:\brave\3\src\brave\node_modules\jsdom\lib\jsdom\browser\Window.js:866:7    at Object.lock (D:\brave\3\src\brave\components\brave_wallet_ui\common\async\__mocks__\bridge.ts:577:7)
    at Object.attemptPasswordEntry (D:\brave\3\src\brave\components\brave_wallet_ui\common\hooks\use-password-attempts.ts:48:26)
    at D:\brave\3\src\brave\components\brave_wallet_ui\common\hooks\use-password-attempts.test.tsx:58:7 undefined

<...>

 PASS  components/brave_wallet_ui/common/hooks/use-password-attempts.test.tsx   
  usePasswordAttempts hook
    √ should increment attempts on bad password & lock wallet after 3 failed attempts (56 ms)
    √ should return "true" for valid password (4 ms)
    √ should return "false" for invalid password (3 ms)

Test Suites: 1 passed, 1 total
Tests:       3 passed, 3 total
Snapshots:   0 total
Time:        1.751 s, estimated 4 s