fix(test): suppress InteractionManager deprecation warning in CI logs

[grimen]

Summary

Fixes #3813.

Every suite that renders a navigator (or otherwise touches InteractionManager) re-triggers React Native's InteractionManager has been deprecated warning once per test file (warnOnce dedupes per module registry, and Jest resets the registry per file), flooding Concourse/CI logs with repeated warning + stack-trace noise.

Changes

• jest.setup.js (new): wraps console.warn and drops only messages matching InteractionManager has been deprecated — and only when CI is set, so the deprecation stays visible in local dev runs. All other warnings pass through untouched.
• jest.config.js: registers the setup file via setupFilesAfterEnv (re-applied per test file, so it survives Jest's per-file module resets).
• ci/pipeline.yml: adds params: { CI: true } to the Concourse test-unit task. GitHub Actions sets CI=true automatically, but Concourse deliberately does not expose build-metadata env vars to task containers (Access metadata from task concourse/concourse#790), so it must be set explicitly — same convention the build tasks already use.

Why not fix the root cause instead

• @react-navigation v7 (current, latest stable) still uses InteractionManager; it is only removed in v8, which is alpha-only today and a breaking migration.
• The app's own app/screens/transaction-history/transaction-history-screen.tsx also calls InteractionManager.runAfterInteractions directly, so a react-navigation upgrade alone would not silence the warning.

That migration is real future-proofing work but out of scope for this CI-log cleanup; it can be tracked separately.

Test plan

• Local run (no CI): warning still visible — yarn test __tests__/screens/transaction-history-screen.spec.tsx → 1 occurrence, tests pass
• CI=true run: warning suppressed — same spec → 0 occurrences, tests pass
• CI=false behaves like local (warning visible)
• Filter is surgical: a non-matching console.warn still prints under CI=true; only the InteractionManager message is dropped
• Full suite with CI=true: 0 InteractionManager has been deprecated occurrences across all suites; 142 suites pass — the single failure (__tests__/components/blink-card/blink-card.spec.tsx, locale/env-dependent "12/ 28" expectation) fails identically on untouched main
• ci/pipeline.yml still parses as valid YAML (ytt #@ lines are comments)

🤖 Generated with Claude Code

[openoms]

@grimen applied the ci change from here so Concourse adds the CI=true env:

./ci/repipe
Updating pipeline @ ciblink
could not find a valid token.
logging in to team 'dev'

navigate to the following URL in your browser:

  https://ci.blink.sv/login?fly_port=57809

target saved
jobs:
  job test-unit has changed:
  name: test-unit
  plan:
  - in_parallel:
      steps:
      - get: repo
        trigger: true
      - get: bundled-deps
        trigger: true
      - get: pipeline-tasks
  - config:
      image_resource:
        name: ""
        source:
          password: ((docker-creds.password))
          repository: us.gcr.io/galoy-org/galoy-mobile-pipeline
          username: ((docker-creds.username))
        type: registry-image
      inputs:
      - name: bundled-deps
      - name: pipeline-tasks
      - name: repo
+     params:
+       CI: "true"
      platform: linux
      run:
        path: pipeline-tasks/ci/tasks/test-unit.sh
    task: test-unit
  
pipeline name: blink-mobile

apply configuration? [yN]: y
configuration updated
unpaused 'blink-mobile'