Add "restart" logic that is easily engageable from IDEs

[JamesHutchison]

The current behavior of the daemon is:

• if you run a test and the daemon isn't running, it is started
• you're stuck with the daemon server until you start it again, manually

I can see how this may be cumbersome. This issue is to add an argument that specifies the restart frequency for a test. Basically, if you rerun a single test X times in X seconds, it'll restart the server. Server restarts are necessary for when you encounter test logic that isn't properly isolated, which will probably be more often than one thinks.

[JamesHutchison]

Also, jurigged can get in a bad state due to no fault of the user. I encountered this when changing assert 1 == 1 to assert 1 == 2 and then back to assert 1 == 1.

[JamesHutchison]

Currently things are more stable than before, and there's a restart command, so going to move this to deprioritized