Expose `StartWorkflowExecutionResponse` fields to `ExecuteWorkflow` API

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

ExecuteWorkflow wraps StartWorkflowExecution call, and don't provide visibility to the StartWorkflowExecutionResponse. In particular, if the workflow ID conflict policy is UseExisting, the StartWorkflowExecutionResponse contains the boolean Started which indicates if the call actually started a new workflow or not. It might also contain a link that can also be useful.

For Nexus WorkflowRunOperation, it would need the link that being added in https://github.com/temporalio/api/pull/563.

Describe the solution you'd like

We want to provide some of the information in StartWorkflowExecutionResponse. This can achieved if we add a optional object pointer in StartWorkflowOptions that can be populated by the SDK internals. Example solution:

type StartWorkflowResultInfo struct {
	Link *commonpb.Link
}

type StartWorkflowOptions struct {
	...
	ResultInfo *StartWorkflowResultInfo
}

func ExecuteWorkflow(...) (...) {
	...

	if options.ResultInfo != nil {
		options.ResultInfo.Link = resp.Link
	}
}

Per-SDK Tickets

• Go -
• Java -
• Core -
• TypeScript -
• Python -
• .NET -
• Ruby -
• PHP -
• Temporal CLI -

Start with the ExecuteWorkflow API and StartWorkflowOptions, then compare the available StartWorkflowExecutionResponse fields, especially Started and Link. Review how the proposed ResultInfo object would be populated by SDK internals and track the Go, Java, Core, TypeScript, Python, .NET, Ruby, PHP, and CLI tickets. Done means the required response information is exposed through the relevant SDK APIs.