chore(test): revive jest suite (ttypescript→ts-patch, ts-jest pin, native mocks)

[islandbitcoin]

Summary

The Jest unit-test suite could not run at all (0 tests executable). This PR fixes the toolchain so the suite runs again. It went from 0 → ~119 passing locally.

This is infra only — no app/source code is changed.

Root causes & fixes

1. ttypescript is unmaintained & incompatible with TS 5.x (Cannot set property createProgram).

   • Migrated to ts-patch (the maintained successor that ts-auto-mock itself uses).
   • Added ts-patch dep + a hack:ts-patch script wired into the existing prepare hook.
   • Switched the ts-jest compiler to the standard "typescript", which ts-patch patches in place to enable the ts-auto-mock transformer declared in tsconfig.jest.json.

2. ts-jest floated to 29.4.x, which requires ts.JSDocParsingMode.ParseAll (TS 5.3+) and crashes on the pinned typescript@5.0.4 (Cannot read properties of undefined (reading 'ParseAll')).

   • Pinned ts-jest to ~29.2.6 (last line without that requirement).

3. Pre-existing cross-file type errors aborted the whole run.

   • Set ts-jest diagnostics: { warnOnly: true } so type errors are surfaced as warnings without killing the runner.

4. Native modules crash at import time under jest.

   • Added manual mocks: react-native-fs, react-native-keychain, react-native-share, @breeztech/breez-sdk-spark-react-native, @breeztech/react-native-breez-sdk-liquid, and @env (+ moduleNameMapper).
   • Rewrote the AsyncStorage mock, whose re-export resolved to undefined and broke redux-persist (config.storage is required).

5. ESM-only packages (@reduxjs/toolkit v2, react-redux, uuid) resolve via the react-native export condition to ESM/source jest can't parse.

   • Added a custom jest.resolver.js that forces those through their CommonJS condition, added cjs/mjs to moduleFileExtensions, and extended transformIgnorePatterns.

Result

• Before: suite fails to compile, 0 tests run.
• After: ~119 passing, 18 failing.

The remaining failures are pre-existing and out of scope for this PR:

• Test/code assertion drift (URI formats, btc address, creation-data defaults).
• Breez SDK Spark migration (Breez SDK Spark migration #585) tests that were never updated for the native SDK (Breez SDK not initialized).
• Screen tests that still need redux store/persist bootstrapping + a longer ESM resolver allowlist.

Test plan

yarn install        # runs ts-patch install via prepare hook
yarn jest --runInBand

Expect the suite to run (no compile error) with ~119 passing.

[linear]

ENG-421

[islandbitcoin]

Closing as superseded.

This PR fixes the jest-suite load failure via ts-patch (compiler: "typescript" + hack:ts-patch install). In the meantime, feat/fygaro solved the same problem a different way — ts-jest astTransformers with a ts-auto-mock wrapper and no ts-patch (commit a1c07eb, "run spec without ttypescript"). That approach is already on feat/fygaro and rides to main via #621, so merging this would re-introduce ts-patch and conflict with the astTransformers setup.

It's also stale — its merge-base with feat/fygaro is still the original branch point; it never caught up (still pins Node 18 in test.yml, predating the #638 Node-20 bump).

What's still valuable here are the native mocks this added and feat/fygaro still lacks (__mocks__/@breeztech/*, env, react-native-fs, react-native-keychain, react-native-share, jest.resolver.js). Salvaging those (re-validated against the astTransformers setup, not ts-patch) + greening the full suite is tracked in ENG-433. The remaining Check Code gate (the ~82 tsc errors) is ENG-425.

ENG-421 (the load-failure ticket this PR was opened for) is effectively resolved by the astTransformers approach on feat/fygaro.