functional-tests: Add a way to track MinerFS status changes
This re-introduces a feature that I previously removed, as it turns out the 601-applications-sync test requires this feature. In general, tests that trigger miner-fs operations should continue to use await_resource_inserted() and await_resource_deleted(). For cases where we expect the miner to wake up but to not make any database changes (because they have already been made) it's now possible to use the new MinerFsHelper.await_wakeup_count() function.
Showing with 70 additions and 0 deletions