Improve the reliability of windows time based actions

[TrentHouliston]

Occasionally in CI, the chrono controller would fail to stop and continue to run even after shutdown had happened.

Looking at the traces it seems that the shutdown from chrono controller stays running forever as well as chrono controller continuing to emit tasks.

The only way this could happen is if shutdown failed to acquire the mutex forever.

By setting running to false first outside of the mutex the main chrono thread should stop emitting tasks if it's looping.

If it's sleeping on the condition variable then locking the mutex then notifying should ensure it wakes up.

Also when windows ran tests, often they would time out.
This was because the timer that was used for sleeping would often vastly overestimate the amount of sleep time.
For example, the sleep for 1ms tests were often sleeping for 15 to 30ms instead.