Added test for the case that rhythm was inactive for a few days and

Added test for the case that rhythm was inactive for a few days and
needs to "make up" beats. Because this required changing db data in the
test I discovered a locking bug by writing this test.  The locking changes
I made here may be sufficient to allow for a concurrent deployment of rhythm.
Maybe.  But that should be tested to be sure.