💥 Use context-sensitive randomness for workflow views

[eamsden]

What was changed

Track privately whether a workflow context view requires replay-safe randomness. All replayable execution uses workflow randomness. Queries, update validators, and patch activation callbacks use system randomness.

Breaking change

WorkflowContextView and the containing PatchActivationInput are no longer Send or Sync.

Why?

Allow telemetry and tracing to safely generate identifiers with replayable randomness where appropriate, while using system randomness when history cannot be recorded and thus advancing workflow random streams would likely cause non-deterministic execution.

Checklist

1. Closes N/A — no linked issue.

2. How was this tested:

   • cargo +nightly fmt
   • cargo test -p temporalio-workflow --lib
   • cargo check -p temporalio-workflow --target wasm32-unknown-unknown
   • cargo integ-test -t wasm_workflow_tests -- --test-threads 1
   • cargo lint
   • cargo test-lint
   • git diff --check

3. Any docs updates needed?

   • The root CHANGELOG.md documents the breaking auto-trait change.
   • No docs.temporal.io update is needed.