port mutex sample from go repository

[K-Yo]

What was changed

Added a python sample for mutex pattern

Why?

The sample exists for go sdk but not for python yet. I needed it so I figured I could share it.

Checklist

1. TODO

I’ve left a TODO in the code, I am not sure how to properly distinguish who sends a release in python (even if sender workflows are supposed to send them in order)

3. How was this tested:

ran it locally with latest temporal dev server, and using branch pyproject.toml configuration.

4. Any docs updates needed?

not that I think of

[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]

I think we may not want to blind-port this from Go but have a more Pythonic way to do a mutex and we want to make sure workflows are in their own files separate from activities/models. For instance, the .NET version of this sample at https://github.com/temporalio/samples-dotnet/tree/main/src/Mutex made an idiomatic WorkflowMutex class for general purpose use. I think this sample should consider a workflow-backed Lock class that looks almost exactly like https://docs.python.org/3/library/asyncio-sync.html#asyncio.Lock and is copyable/usable as if it is a library.

[p44ytwz25w-cloud]

write permissions required into the code before lock can be engaged

[brianstrauch]

@K-Yo — checking in here, sorry for the long delay. Still interested in reworking it? If we don't hear back in the next couple of weeks we'll close it out, and you're welcome to reopen whenever.