Unit test for non-deterministic errors

[yux0]

Is your feature request related to a problem? Please describe.
To detect non-deterministic errors with the unit test framework

Proposed Solution
This is a draft idea about the unit testing.

Users define the possible workflow inputs, signal inputs, marker outputs, activity inputs/outputs. The testing framework generates all decision branches and tests them with the replay test to detect NDE.

The detail of compare workflow history from two versions is not determined and requires some polishes.

Additional context
Add any other context or screenshots about the feature request here.

[ibarrajo]

We have implemented shadower and replayer tests that ingest history and replay in order to find non-deterministic errors:

https://cadenceworkflow.io/docs/go-client/workflow-replay-shadowing/