More thorough nondeterminism checking

I noticed when trying to create nondeterminism in an orchestrator on purpose that DTFx does not do a very good job at detecting it. It is surprisingly tolerant.

It appears that all it does is essentially to count the orchestrator actions. It matches actions based on their position in the sequence (the EventId); but it does not check if the replayed actions match the history event details (type, arguments, etc).

I think it could perhaps be helpful to do a more precise check and throw a `NondeterminismDetectedException` with a detailed description of the divergence situation (including details about the expected and actual events).

Perhaps this can be an optional feature so as to not break legacy deployments.

Inizia esaminando il replay corrente dell’orchestratore di DTFx e il comportamento di corrispondenza di azioni/EventId, quindi riproduci l’orchestratore intenzionalmente non deterministico descritto nell’issue. Confronta le azioni riprodotte con i tipi di evento e gli argomenti della cronologia, e chiarisci il comportamento opzionale previsto e i requisiti di compatibilità per NondeterminismDetectedException.

Scritto dal modello di indicizzazione a partire dal testo della issue.