Improve ExecutionStartToCloseTimeoutSeconds in Go Client Tests

[natemort]

Is your feature request related to a problem? Please describe.
This relates to the Go client, putting it here for consolidation.

Within a Workflow you may inspect the ExecutionStartToCloseTimeoutSeconds via:

workflow.GetInfo(ctx).ExecutionStartToCloseTimeoutSeconds

In the TestWorkflowEnvironment this always has a value of 1 second, even thought we have TestWorkflowEnvironment.SetWorkflowTimeout which explicitly allows for controlling the workflow timeout.

Proposed Solution
Update the test WorkflowInfo's ExecutionStartToCloseTimeoutSeconds to match the execution timeout specified to the TestWorkflowEnvironment.

Additional context
Add any other context or screenshots about the feature request here.

[BrysonUrie]

I would love to take a look at this if thats alright! (newbie)

[mkamilli]

I’ve opened a PR to fix it. @natemort, could you pls take a look?

cadence-workflow/cadence-go-client#1482