Remove ENABLE_AI_PATCHING_CORRECTNESS_CHECKS feature flag -> enable the feature everywhere

[jurgenwerk]

This flag's purpose was to iterate on the feature's development while having it checked in in main. Now that we tested it in staging and it looks good, I think we can simply get rid of the conditional behavior.

[github-actions]

Host Test Results

    1 files  ± 0      1 suites  ±0   1h 34m 0s ⏱️ +17s
1 821 tests +18  1 807 ✅ +19  14 💤 ±0  0 ❌ ±0 
1 840 runs  +19  1 826 ✅ +21  14 💤 ±0  0 ❌  - 1 

Results for commit 5ea9ce7. ± Comparison against base commit 5218788.

This pull request removes 1 and adds 19 tests. Note that renamed tests count towards both.

Chrome ‑ error

Chrome ‑ Integration | CardDef-FieldDef relationships test: CardDef field (plural) linked to from a FieldDef renders in atom format
Chrome ‑ Integration | CardDef-FieldDef relationships test: compound field (plural) contained in a FieldDef renders in atom format (read-only)
Chrome ‑ Integration | CardDef-FieldDef relationships test: primitive field (plural) contained in a FieldDef is read-only
Chrome ‑ Integration | CardDef-FieldDef relationships test: render a CardDef field (singular) linked to from a FieldDef
Chrome ‑ Integration | field configuration: configuration reacts when a consumed linked card field value changes
Chrome ‑ Integration | field configuration: configuration reacts when a linked relationship loads
Chrome ‑ Integration | field configuration: configuration reacts when a parent attribute changes
Chrome ‑ Integration | field configuration: linksTo field passes configuration to embedded card formats
Chrome ‑ Integration | field configuration: linksToMany field passes configuration to embedded card formats
Chrome ‑ Integration | field configuration: merged configuration is injected into field format component
…