[codex] Fix watcher repair while Codex is running

[Adidas8023]

Summary

• allow watcher-triggered repair to patch Codex.app on disk even when Codex is currently running
• keep interactive repair behavior unchanged: it still asks before repatching a running macOS app
• add regression tests for watcher vs interactive running-app repair behavior

Root cause

After a Codex app update, the official app bundle replaces the patched app.asar and removes the Codex++ loader. The watcher then sees Codex already running without Codex++; the current repair path can postpone before writing the loader back, so the app stays unpatched even after restart attempts.

Watcher repair is better handled by repairing the app on disk first, then asking the user to restart so the already-running process can load the patched app on next launch.

Validation

• node --import tsx --test packages/installer/test/repair-running-codex.test.ts
• npm test
• npm run build

Related: #251, #253