Right now, sippy doesn't directly report mco-disruptive suite only tests (i.e. slow MCN tests and OCL tests) to component readiness.

In 4.21+ we should try to get mco disruptive to candidate (not immediately blocking) or standard (eventually informing/blocking) so regressions gets reported in sippy component readiness.

Disruptive is auto hidden atm due to it filtering https://github.com/openshift/sippy/blob/main/pkg/variantregistry/ocp.go#L662 , we should create a mco-disruptive filter right above and mark as candidate/standard