Waiting on update result should auto-skip time in time-skipping environments

[cretz]

Describe the solution you'd like

Today in time-skipping environments, we auto-skip time when waiting on workflow results. We should do the same when waiting on update results.

Per-SDK Tickets

• Go - N/A (no time-skipping environment)
• Java - Auto-skip time in time-skipping testing environment when waiting on update result sdk-java#2283
• Core - N/A (no time-skipping environment)
• TypeScript - [Feature Request] Auto-skip time in time-skipping testing environment when waiting on update result sdk-typescript#1549
• Python - [Feature Request] Auto-skip time in time-skipping testing environment when waiting on update result sdk-python#675
• .NET - [Feature Request] Auto-skip time in time-skipping testing environment when waiting on update result sdk-dotnet#360
• Ruby - N/A (workflows not built yet)
• PHP - N/A (no time-skipping environment)
• Temporal CLI - (no time-skipping environment)

[josh-berry]

Per team discussion, we don't want to take this approach—this is problematic because the client is the one who says "start/stop skipping time", so there is a race between the client receiving the update result and time-skipping being stopped. During this window, we'd still be time-skipping over potentially arbitrary other events in the workflow (until the "stop time skipping" message arrives). There is also the problem that Updates run concurrently with other things in the same workflow, and it may not be appropriate to skip time for those other things.

A couple approaches here:

1. Make the server handle starting/stopping time-skipping.
2. Do nothing and document that users need to manually control when to skip and when not to skip. Then users can make more informed decisions that are specific to their particular scenario.