Fix: add missing simulator QA harness types so the app compiles

[justanotheratom]

Problem

The Maestro simulator test harness (PRs #114–#116) references three types that were never committed, so the IngrediCheck app target currently fails to build on main:

• DebugScanQAMode (.isEnabled, .presets) — referenced by SplashScreen, HomeView, ScanCameraView, and DebugBarcodeInjectorSheet
• AppRuntimePolicy (.disablesAnalytics, .skipsDeviceRegistration, .usesLocalUITestAuth) — referenced by AuthController and AnalyticsService

The README for the Maestro suite even lists "the app branch containing DebugScanQAMode" as a prerequisite, but the type was never landed.

Fix

Adds both types to IngrediCheck/Testing/UITestHarness.swift (alongside the existing UITestHarness), with behavior reconstructed from their call sites:

• DebugScanQAMode mirrors UITestHarness's --debug-scan-qa launch-argument parsing (simulator-only) and exposes the barcode-injector presets. Preset labels match exactly what the scan flows tap ("Coca-Cola 12 oz", "Invalid") and map to the barcodes seeded in UITestFixtures.makeScans().
• AppRuntimePolicy centralizes the simulator-isolation switches: suppress analytics and backend device registration under any automated run, and gate the local fake-session path to the fully-mocked UITestHarness flows.

Verification

Built for the iOS 17 simulator and ran the full 63-flow Maestro suite (.maestro/flows):

• 61 / 63 pass, including all scan/* injector flows.
• The 2 remaining failures (settings/10_sign_out_confirm, settings/12_delete_account_dialog) are pre-existing and unrelated to this change: after sign-out the app lands on WelcomeView instead of presenting sign_in_sheet, because the onChange(of: authController.signInState) handler in SplashScreen.swift is commented out. Tracked separately.

Note: the suite was run with a placeholder Config.swift (gitignored). The mocked UITestHarness flows don't need real backend credentials.

🤖 Generated with Claude Code