chore(MSP-5160): disallow timeouts for Infection, setting maxTimeouts to 0

Why?

See https://infection.github.io/2026/01/14/whats-new-in-0.32.3/

in a nutshell:

> Slow CI accumulation: You get timeouts to zero, the build is fast. You add a new feature - suddenly 20 new timeouts. Your CI now takes minutes longer. The worst part? There’s no way to know they exist without digging through logs.

> Hidden infinite loops: Some timeouts are simple performance hits on slow CI. Others are mutations that create infinite loops-the very test gaps Infection is supposed to find, now hidden among “acceptable” slowdowns.

Author: maks-rafalko

infection.json5

@@ -7,5 +7,6 @@
   },
   "mutators": {
     "@default": true
-  }
+  },
+  "maxTimeouts": 0
 }