Clean up active/passive revocation tests

Amend tests to no longer assert an error message upon active revocation
and to instead validate the success on either revocation variant,
reflecting previous changes.

In theory the "Passive" boolean seems removable as it does not add any
functionality besides being logged, but it was found some instances of
it are still needed to block active revocation for SSH certificates.

Signed-off-by: Georg Pfuetzenreuter <georg.pfuetzenreuter@suse.com>

Author: tacerus

api/revoke_test.go

@@ -43,19 +43,18 @@ func TestRevokeRequestValidate(t *testing.T) {
 			},
 			err: &errs.Error{Err: errors.New("reasonCode out of bounds"), Status: http.StatusBadRequest},
 		},
-		"error/non-passive not implemented": {
+		"ok/passive": {
 			rr: &RevokeRequest{
 				Serial:     "10",
-				ReasonCode: 8,
-				Passive:    false,
+				ReasonCode: 9,
+				Passive:    true,
 			},
-			err: &errs.Error{Err: errors.New("non-passive revocation not implemented"), Status: http.StatusNotImplemented},
 		},
-		"ok": {
+		"ok/active": {
 			rr: &RevokeRequest{
 				Serial:     "10",
 				ReasonCode: 9,
-				Passive:    true,
+				Passive:    false,
 			},
 		},
 	}