Test: scheduler: update tests for digest fix
    
    This has been bugging me for years!
    
    There are still a few regression tests where fencing devices are sanitized
    (i.e.  have a parameter value of "****") and yet are still restarting. These
    are all correct, because either some value not marked as private (e.g. "user")
    was sanitized, or they pre-date op-secure-params and op-secure-digest.
    
    patch_name: 006-digests.patch
    present_in_specfile: true
    location_in_specfile: 6
    squash_commits: true