Properly update workflow transition history

[yycptt]

What changed?

• Properly update workflow transition history.
• Only update transition history when closing transaction as active
• Only update updates to replicated application state as state transition (NOTE: this is a different concept from the existing state transition counter we have in executionInfo, which is simply how many times the mutable state object got updated.)
  • When sub state machine tree is dirty
  • When history event got generated.
  • When there's sync activity
  • All other changes are either system level field update or not replicated (e.g. buffer events or transient workflow task)

Why?

• State-based replication rely on all clusters agree on the same transition history. and replication task processing logic relies on the transition history to detect missing or conflicting state transitions.

How did you test it?

• Existing tests
• Added unit tests

Potential risks

• State transition history is behind a feature flag so no risk.

Documentation

• N/A

Is hotfix candidate?

• No