ZTS: Retry redundancy_draid_spare[1,3].ksh

The redundancy_draid_spare1.ksh and redundancy_draid_spare3.ksh test
cases are a little to strict for the sequential resilver case.  While
unlikely it is possible that a handful of correctable checksum errors
will be reported resulting in a test failure.  Update the zts-report.py
script to allow this the test case to be retried if requested.

Reviewed-by: George Melikov <mail@gmelikov.ru>
Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov>
Closes #13318

tests/test-runner/bin/zts-report.py.in

@@ -225,7 +225,8 @@ maybe = {
     'pool_checkpoint/checkpoint_discard_busy': ['FAIL', 11946],
     'projectquota/setup': ['SKIP', exec_reason],
     'redundancy/redundancy_004_neg': ['FAIL', 7290],
-    'redundancy/redundancy_draid_spare3': ['SKIP', known_reason],
+    'redundancy/redundancy_draid_spare1': ['FAIL', known_reason],
+    'redundancy/redundancy_draid_spare3': ['FAIL', known_reason],
     'removal/removal_condense_export': ['FAIL', known_reason],
     'reservation/reservation_008_pos': ['FAIL', 7741],
     'reservation/reservation_018_pos': ['FAIL', 5642],

tests/zfs-tests/tests/functional/redundancy/redundancy_draid_spare3.ksh

@@ -48,10 +48,6 @@ function cleanup_tunable
 
 log_onexit cleanup_tunable
 
-if is_kmemleak; then
-	log_unsupported "Test case runs slowly when kmemleak is enabled"
-fi
-
 #
 # Disable scrubbing after a sequential resilver to verify the resilver
 # alone is able to reconstruct the data without the help of a scrub.