Added C# workflow versioning tutorial

[WhitWaldo]

Description

Added project demonstrating patch and name-based versioning in the .NET SDK.

This is implemented to align with the style used in the Python example though I took the liberty of adding some logging to better demonstrate to the user which path is called when it runs and to explain various aspects of the implementation.

Issue reference

We strive to have all PRs being opened based on an issue, where the problem or feature have been discussed prior to implementation.

Please reference the issue this PR will close: #1279

Checklist

Please make sure you've completed the relevant tasks for this PR, out of the following list:

• The quickstart code compiles correctly
• You've tested new builds of the quickstart if you changed quickstart code
• You've updated the quickstart's README if necessary
• If you have changed the steps for a quickstart be sure that you have updated the automated validation accordingly. All of our quickstarts have annotations that allow them to be executed automatically as code. For more information see mechanical-markdown. For user guide with examples see Examples.

[alicejgibbons]

I prefer the ordering of this example to the python one because as @WhitWaldo rightly points out people would likely patch a workflow first before migrating to a new named version. This version goes in that order which makes more sense from a use case/best practices perspective.

Will let @marcduiker have final review for Dapr university

[alicejgibbons]

Getting there! a few changes for consistency

[WhitWaldo]

@alicejgibbons DCO check is bugged and should be ignored. All my commits are signed with the appropriate (and unchanged) email address.

[marcduiker]

LGTM