Implement single-instance enforcement using a named mutex to prevent multiple CoreCycler instances from running simultaneously.

[cal4]

No description provided.

[sp00n]

Hm. Not sure I want to add this.
Some people are actually deliberately using multiple instances of CoreCycler to test for specific load scenarios, and while CoreCycler was never intended to work that way, it seems to be a valid use case.

[cal4]

It could be disabled by default and opted-in via config

[cal4]

And to explain my usecase. I run this script on a nightly basis via Task Scheduler. No problems if a single instance is runnning, but I've noticed wonkiness when multiple instances run at the same time (didn't realize this is a use-case, but causes trouble for me). I tried using Task Scheduler's solution to run a single instance (see below), but it didn't work. Figured just baking it into the script would be the most portable/reusable solution rather than adapting for Windows Task Scheduler.