Za/konaproofs docs

[ZakAyesh]

Add info about Kona proofs in the fault proofs explainer

[Inphi]

Looks good overall. One consideration I just realized is that dispute-mon may receive spurious alerts if a chain operators executes U18 (so they have cannon and cannon+kona configured in the dispute game factory) and someone creates invalid CANNON_KONA games.
If the chain operator isn't running a cannon-kona challenger, then the invalid CANNON_KONA games would be undisputed and resolve (incorrectly); tripping up the dispute-mon. Dispute-mon does not discriminate between respected and non-respected game types; it monitors all game types configured in the factory. So for this reason, we should recommend that operators configure their op-challenger for cannon-kona, even if it's not respected.

That said, a cannon-kona game that isn't respected cannot break the anchor state registry, even if it resolves incorrectly. This recommendation is to avoid spurious alerts, however unlikely, from being triggered by op-dispute-mon.