Mechanism to control WorkflowIdReusePolicy at the Workflow definition/implementation

Maxim said to create a feature request for this

Right now, this policy is set by the client before start the workflow execution. This means different client can use different policy. It might be useful to have a mechanism to give the option to lock this policy at the workflow definition/implementation level, so no client can mess it up. Maybe have it on WorkflowServiceStubsOptions