Cascade terminate/purge support in GrpcDurableTaskClient

[Shivam Kumar (shivamkm07)]

This PR adds support to recursively terminate/purge sub-orchestrations in GrpcDurableTaskClient. It also sets the recursive behavior to be false by default.

Closes: #260

[Jacob Viau (jviau)]

As we now have multiple parameters for terminate, I recommend we do the following:

1. Add TerminateInstanceOptions
2. Make the current abstract method virtual. Default implementation will call one of the new methods we add.
3. Add TerminateInstanceOptions accepting virtual methods
4. Update our clients to override the new options-receiving method.

/// add xmldocpublicrecordTerminateInstanceOptions{publicobject?Output{get;init;}publicboolRecursive{get;init;}}

new methods:

publicvirtualTaskTerminateInstanceAsync(stringinstanceId,TerminateInstanceOptions?options,CancellationTokencancellation)=>thrownewNotSupportedException($"{this.GetType()} does not support orchestration termination.");// this is the formerly abstract methodpublicvirtualTaskTerminateInstanceAsync(stringinstanceId,object?output=null,CancellationTokencancellation=default){TerminateInstanceOptions?options=outputisnull?null:new(){Output=output};returnthis.TerminateInstanceAsync(instanceId,options,cancellation);}

[Shivam Kumar (shivamkm07)]

As we now have multiple parameters for terminate, I recommend we do the following:

1. Add TerminateInstanceOptions
2. Make the current abstract method virtual. Default implementation will call one of the new methods we add.
3. Add TerminateInstanceOptions accepting virtual methods
4. Update our clients to override the new options-receiving method.

/// add xmldocpublicrecordTerminateInstanceOptions{publicobject?Output{get;init;}publicboolRecursive{get;init;}}

new methods:

publicvirtualTaskTerminateInstanceAsync(stringinstanceId,TerminateInstanceOptions?options,CancellationTokencancellation)=>thrownewNotSupportedException($"{this.GetType()} does not support orchestration termination.");// this is the formerly abstract methodpublicvirtualTaskTerminateInstanceAsync(stringinstanceId,object?output=null,CancellationTokencancellation=default){TerminateInstanceOptions?options=outputisnull?null:new(){Output=output};returnthis.TerminateInstanceAsync(instanceId,options,cancellation);}

I am okay with this change. Just should the new TerminateInstanceOptions method be an abstract method and both GrpcDurableTaskClient and ShimDurableTaskClient implement this method? This is what seems to be followed in other DurableTaskClient methods..

[Shivam Kumar (shivamkm07)]

As we now have multiple parameters for terminate, I recommend we do the following:

1. Add TerminateInstanceOptions
2. Make the current abstract method virtual. Default implementation will call one of the new methods we add.
3. Add TerminateInstanceOptions accepting virtual methods
4. Update our clients to override the new options-receiving method.

/// add xmldocpublicrecordTerminateInstanceOptions{publicobject?Output{get;init;}publicboolRecursive{get;init;}}

new methods:

publicvirtualTaskTerminateInstanceAsync(stringinstanceId,TerminateInstanceOptions?options,CancellationTokencancellation)=>thrownewNotSupportedException($"{this.GetType()} does not support orchestration termination.");// this is the formerly abstract methodpublicvirtualTaskTerminateInstanceAsync(stringinstanceId,object?output=null,CancellationTokencancellation=default){TerminateInstanceOptions?options=outputisnull?null:new(){Output=output};returnthis.TerminateInstanceAsync(instanceId,options,cancellation);}

Jacob Viau (@jviau) Pushed the suggested changes. Please review.

[Jacob Viau (jviau)]

Only a few small comments of recursive default behavior.