Make WorkflowState publically constructable so it can be used in tests by consumers

[SrChronus]

Describe the feature

We have a control flow that uses workflow state to make decisions. up until v17 we were able to construct the WorkflowState with some reflection to test our code. This is no longer possible which means we can't test our code anymore.

Release Note

RELEASE NOTE:

[WhitWaldo]

Would you be able to get into more detail about what you mean? Looking at the WorkflowState of then and now, the only difference I see is that I've got the new type marked as sealed, but either one has an internal constructor.

I've put a little more thought into this - I can unseal the type and mark the properties as virtual. I'd leave the current constructor as internal, but add a protected constructor you can use for testing. This shouldn't be a breaking change and I'd be happy to do it as a patch.

[SrChronus]

the issue is that peviously we could use OrchestrationMetadata as a parameter to call the constructor with as that was a public type.
As of your change the constructor requires WorkflowMetadata which is internal so we can't construct that even with reflection.

If your proposed solution would provide a parameterless protected constructor with the virtual properties then all our issues would be solved indeed!

I'd love to see that implemented