[Feature Request] Support for WorkflowIdConflictPolicy

[stephanos]

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

The Start Workflow and Signal-with-Start APIs has a new field, WorkflowIdConflictPolicy.

Support for the new policy in both APIs is needed.

Furthermore, the comments should emphasize that WorkflowIdReusePolicy is for closed Workflows, and WorkflowIdConflictPolicy` is for running Workflows.

Describe the solution you'd like

A new field/parameter in each SDK's Start Workflow and Signal-With-Start API struct/function.

• Go - Support for WorkflowIdConflictPolicy sdk-go#1447
• Java - Support for WorkflowIdConflictPolicy sdk-java#2033
• Core (maybe nothing required but proto update) - Support for WorkflowIdConflictPolicy sdk-core#715
• TypeScript (after core) - Support for WorkflowIdConflictPolicy sdk-typescript#1392
• Python (after core) - Support for WorkflowIdConflictPolicy sdk-python#504
• .NET (after core) - Support for WorkflowIdConflictPolicy sdk-dotnet#217
• .NET follow-up Support WorkflowIdConflictPolicy for Signal-With-Start API sdk-dotnet#316
• CLI (after Go) - Support for WorkflowIdConflictPolicy cli#528
• PHP (after Go) - Support for WorkflowIdConflictPolicy sdk-php#416

Additional context

See temporalio/api#359.

[cretz]

Updated description to add checkboxes for each SDK. Feel free to create issues/PRs as needed.

[stephanos]

@cretz should the CLI be tracked here, too, or elsewhere?

[cretz]

Here is good, I added a checkbox. If/when ready, issues can be created in each repo.