PRR: fix rollback metrics detection

Count of pods in failed + SMTAlignmentError can be used to decide a
rollback.

Signed-off-by: Francesco Romani <[email protected]>

Author: ffromani

keps/sig-node/2625-cpumanager-policies-thread-placement/README.md

@@ -280,7 +280,8 @@ No changes needed
 ### Rollout, Upgrade and Rollback Planning
 
 * **How can a rollout fail? Can it impact already running workloads?** Kubelet may fail to start. The kubelet may crash.
-* **What specific metrics should inform a rollback?** Not applicable
+* **What specific metrics should inform a rollback?**
+  - the number of pod ending up in Failed for SMTAlignmentError could be used to decide a rollback.
 * **Were upgrade and rollback tested? Was upgrade->downgrade->upgrade path tested?** Not Applicable.
 * **Is the rollout accompanied by any deprecations and/or removals of features,  APIs, fields of API types, flags, etc.?** No.
 

keps/sig-node/2625-cpumanager-policies-thread-placement/kep.yaml

@@ -35,7 +35,7 @@ feature-gates:
   - name: "CPUManagerPolicyOptions"
     components:
       - kubelet
-disable-supported: false
+disable-supported: true
 
 # The following PRR answers are required at beta release
 metrics: []