[Feature Request] Serialization context for codecs and converters

Is your feature request related to a problem? Please describe.

When serializing/deserializing a payload for a workflow or activity users payload codec/converter may want to know details about the payloads context. For example with workflow input/output, the context could include workflow ID. This can be useful if the users want to sign the payload with the workflowID to help protect against replay attacks.

Describe the solution you'd like

A solution similar to the Java SDK in other languages, see https://github.com/temporalio/sdk-java/pull/1695. Also, make sure that the async activity client gets this context too. Note, this information needs to be available to converters too e.g. for outbound client calls, so it's not just for codecs.

Per-SDK Tickets

• Go - https://github.com/temporalio/sdk-go/issues/1352
• Java - Already exists - https://github.com/temporalio/sdk-java/pull/1695
• Core - N/A
• TypeScript - https://github.com/temporalio/sdk-typescript/issues/1661
• Python - https://github.com/temporalio/sdk-python/issues/796
• .NET - https://github.com/temporalio/sdk-dotnet/issues/438
• Ruby - https://github.com/temporalio/sdk-ruby/issues/238
• PHP - https://github.com/temporalio/sdk-php/issues/587
• Temporal CLI - N/A

Start by reading the linked Java SDK pull request and the per-SDK tickets listed in the issue, especially the unchecked Ruby and PHP items. Compare how the completed SDKs expose serialization context to codecs and converters, then confirm the remaining SDK tickets are implemented and their tests cover workflow, activity, and outbound client payloads.