mutmut run 5 unintuitively does not schedule if cached

[eivindjahren]

When specifying one mutant to rerun, it is not queued if already in cache regardless of whether it passed it failed, just as long as it is not untested. This seems counterintuitive as the user probably has a reason to run that specific one. At the very least, there should be some way of forcing rerun by ignoring the cache.

mutmut/mutmut/__init__.py

Line 719 in 8ee19e9

if cached_status != UNTESTED: