[Feature Request] Dynamic Display Name for Activities in Temporal Go

Currently, when using RegisterActivityWithOptions in Temporal for Go, it is challenging to differentiate between multiple invocations of the same activity method with different parameters. The display name shown in the Temporal UI remains static, making it difficult to identify specific executions.

Requested Feature:

Enable dynamic setting of the display name for activities to improve visibility and distinguish between multiple invocations of the same activity method.

Use Case:

In workflows, a single activity method is invoked more than 10 times, each time with a different purpose passed as parameters. The current static display name does not reflect the specific purpose of each invocation, making it difficult to identify and manage these activities in the Temporal UI.

Proposed Solution:

Allow developers to dynamically set the display name for activities during runtime, possibly by introducing a new option or method within the RegisterActivityWithOptions function.

Start by reviewing the Temporal Go RegisterActivityWithOptions entry point and how activity display names are represented for the Temporal UI. Clarify whether runtime naming belongs to registration or invocation, then define the API, compatibility expectations, and validation path; done when the feature scope is agreed and testable.