SDK support for activity reset

When a user resets an activity the activity should be restarted.

• They may have passed --reset-heartbeats in which case heartbeat details should be cleared
• If they didn't pass it, they may nonetheless want the code to start from the beginning of the method (perhaps they've deployed a code fix which improves efficiency or fixes a memory leak, or have non-deterministic code that has randomly gotten into a bad state.)
  The server will inform the SDK that heartbeats were reset so that it can throw an error in the user's Activity.

Requirements:

• Users shouldn't have to predict that resets will happen when writing their activity code

• Code should by default do the right thing and exit and restart, provided they haven't written an exception handler.

• Should work as much like pause and cancel as possible for consistency.

• Users should be able to write a simple exception handler that cleans up after any interruption, including cancellation, pausing, and reset.

• Users should also be able to differentiate. For example, after cancel, cleanup would be permanent, but after pause/reset, it would be temporary, which may mean the user would want to take different actions.

• Ruby https://github.com/temporalio/sdk-ruby/issues/254

• TypeScript https://github.com/temporalio/sdk-typescript/issues/1693

• Python https://github.com/temporalio/sdk-python/issues/847

• PHP https://github.com/temporalio/sdk-php/issues/605

• Go https://github.com/temporalio/sdk-go/issues/1931

• .NET https://github.com/temporalio/sdk-dotnet/issues/464

• Java https://github.com/temporalio/sdk-java/issues/2488

Start by reading the linked SDK issues for Ruby, TypeScript, Python, PHP, Go, .NET, and Java, then review this repository’s behavior and history compatibility testing context. Done means the listed SDKs support activity reset consistently with pause and cancel, including heartbeat-reset and exception-handling behavior.