Time in Temporal test env

[alex-dixon]

          From #5 

On further examination we can't control time using the test env. In one test our timer was set for 5 seconds, but CI was slow so the timer fired when the test expected it to still be active. This would happen locally but not in CI. Increasing from 5 seconds to 500s fixed the tests. So it's likely not directly caused to having tests with more than one test env / runtime / server, though that will slow down CI significantly, which causes this behavior.

Originally posted by @alex-dixon in #6 (comment)