fixed subsidy limit unittest

Change the test to do stuff instead of just complaining that it can't be done and then failing. I also extended the test a bit to check that the rewards match our published reward schedule (there is an off-by-one error in the documentation revealed by this). I also changed the step size to one, this still only takes ~4 seconds in my VM and allows catching these off-by-one errors.