Workflow Mutex Sample

[devbased]

What was changed

Added a new sample showcasing how to implement a Mutex Workflow for managing concurrent access to a shared resource.

NOTE: Since the required SDK version (the one with workflow history info) hasn't been published yet, I had to add links to the SDK in TemporalioSamples.sln and Directory.build.props

[CLAassistant]

All committers have signed the CLA.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[cretz]

Added some comments, but overall this is the same as I was thinking. I like the idea of wrapping as a utility.

[cretz]

Looks good. Marking approved. I think it can be simplified bit, though I know that file and package sprawl is kinda the .NET way. Approving for CI run, but of course it will fail due to the relative-path dep, no worry there, we can leave this PR open for a bit.

[devbased]

@cretz I reduced the number of files, but I didn't refactor the inputs into nested classes; instead, I placed them outside in the same file where they are being used. Additionally, I provided a bit more detailed description of the project's structure in the README.md

[cretz]

Looks good!

I didn't refactor the inputs into nested classes; instead, I placed them outside in the same file where they are being used.

I think it's clearer as nested classes (I like the type-per-file rule), but not a big deal I suppose.

Will merge when SDK is updated. Thanks!

[cretz]

I opened temporalio/sdk-dotnet#134

[cretz]

Thanks for the update! Gonna merge #39 first if that's ok (unsure if it'll merge cleanly).

[cretz]

Resolved conflict (using GH's built-in conflict editor for the first time, was interesting). Merging once CI passes. Thanks again!