Detect Nexus operation changes during replay

[JSap0914]

What

• compare the service and operation in NexusOperationScheduled history events with the command produced during replay
• report nondeterminism when either value changes
• gate the new checks behind a dedicated Core internal flag so existing histories remain compatible
• add regression coverage and an Unreleased changelog entry

Why

The Nexus operation state machine accepted scheduled history events without validating their service or operation. This allowed workflow code to change either field during replay without raising the non-determinism error used by comparable activity and child-workflow state machines.

Fixes #1231

Tests

• cargo test -p temporalio-sdk-core nexus_operation_state_machine::tests --lib
• cargo test -p temporalio-sdk-core --lib (367 passed, 1 ignored)
• cargo clippy -p temporalio-sdk-core --lib --tests --all-features -- -D warnings
• cargo fmt --all --check
• git diff --check

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[Sushisource]

Thanks for this! Makes perfect sense. I think adding an integration test would be great and then we can merge.

[Sushisource]

@JSap0914 Looks like you need to run the formatter

[Sushisource]

@JSap0914 We'll need you to sign the CLA too :)

[Sushisource]

@JSap0914 - we can merge this if you sign the CLA. Thanks!