Rewrite step definitions with inline detection logic

- Replace abstraction functions with inline regex patterns in step definitions
- Add clear test outcomes: Pass/Fail for testable features, Pending with
  specific prefixes (NOT IMPLEMENTED, CANNOT TEST, WRONG STEP, NOT ON THIS
  SCREEN) for non-testable features
- Fix GherkinHighlighter to use step.text instead of step.originalLine
  for step definition matching
- Update documentation with Test Outcomes section
- Extend test:cucumber script to run all parsing steps

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

features/support/world.ts

@@ -60,7 +60,7 @@ export const screenFieldDetectors: Record<string, Record<string, (source: string
     // EventDetailScreen.tsx lines 77-81: À propos section with description
     'Description': (s) => {
       const match = s.match(/À propos[\s\S]*?<Text[^>]*>([\s\S]*?)<\/Text>/);
-      return match !== null && match[1].trim().length > 50;
+      return match !== null && match[1] !== undefined && match[1].trim().length > 50;
     },
     // EventDetailScreen.tsx lines 8-13: attendees with { name: 'Marie' } rendered via {a.name}
     'Nom': (s) => /name:\s*['"][^'"]+['"]/.test(s) && /\{[^}]*\.name\}/.test(s),