Introduce worker versioning into durable functions

[halspang]

This commit adds the worker versioning options to the base DurableTaskOptions which are read through the host.json file. This change also includes a few changes for wiring the values through as well as testing.

Important

This change depends on multiple external changes/new versions:

• A release containing the changes in DurableTask.Core
• A PR and subsequent release for DurableTask.Abstractions

As is, the tests in this PR will fail due to the lack of appropriate references. Once those releases are made, this PR will have to be updated. However, the code/tests are all complete in their implementation and are OK to be reviewed. This just cannot be merged until that point.

[AnatoliB]

This problem is probably not introduced nor fixable in this PR, but I discovered an issue with orchestration rejection when testing this E2E, so I'll mention it here.

I have an orchestrator like this:

[Function(nameof(WaitForEventOrchestrator))]
public static async Task<string> WaitForEventOrchestrator(
    [OrchestrationTrigger] TaskOrchestrationContext context)
{
    context.SetCustomStatus("Waiting for Continue event...");
    await context.WaitForExternalEvent<object>("Continue");
    context.SetCustomStatus("Continue event received");
    return context.Version;
}

Versioning config in host.json:

"defaultVersion": "2.0",
"versionMatchStrategy": "CurrentOrOlder",
"versionFailureStrategy": "Reject",

When I start an orchestration and it gets paused waiting for an external event, as expected. Next, I shut the worker down, change defaultVersion to 1.0 to emulate the situation when an old worker is still around, start the worker again, and raise the external event. This worker is unable to complete the orchestration, but I'm observing two unexpected side effects:

1. The persisted orchestration history keeps growing, adding EventRaised and orchestratorStarted to the table repeatedly and indefinitely.
2. The custom status disappears.

Both can be significant issues for the user in some contexts.

[halspang]

Updated the code to handle the sub-orchestration version use case you brought up @AnatoliB.

Note that this PR now also depends on this change: microsoft/durabletask-dotnet#437

So that means the dependencies are for a DurableTask.Core release and the packages in the PR above ^

[cgillum]

Some initial feedback. Haven't gone through the whole thing again yet.

[cgillum]

Finished reviewing. Just a couple more things...