move more feature jobs to release-blocking

tests for features like eviction, cpu/memory/topology managers are quite
stable. they should be considered release-blocking

config/jobs/kubernetes/sig-node/containerd.yaml

@@ -550,7 +550,7 @@ periodics:
           cpu: 4
           memory: 6Gi
   annotations:
-    testgrid-dashboards: sig-node-containerd
+    testgrid-dashboards: sig-node-release-blocking
     testgrid-tab-name: node-kubelet-containerd-eviction
     testgrid-alert-email: kubernetes-sig-node-test-failures@googlegroups.com
     description: "Uses kubetest to run node-e2e Eviction tests"

config/jobs/kubernetes/sig-node/node-kubelet.yaml

@@ -734,7 +734,7 @@ periodics:
   interval: 24h
   cluster: k8s-infra-prow-build
   annotations:
-    testgrid-dashboards: sig-node-kubelet
+    testgrid-dashboards: sig-node-release-blocking
     testgrid-tab-name: kubelet-serial-gce-e2e-topology-manager
   labels:
     preset-service-account: "true"
@@ -782,7 +782,7 @@ periodics:
   interval: 24h
   cluster: k8s-infra-prow-build
   annotations:
-    testgrid-dashboards: sig-node-kubelet
+    testgrid-dashboards: sig-node-release-blocking
     testgrid-tab-name: kubelet-serial-gce-e2e-cpu-manager
   labels:
     preset-service-account: "true"
@@ -830,7 +830,7 @@ periodics:
   interval: 24h
   cluster: k8s-infra-prow-build
   annotations:
-    testgrid-dashboards: sig-node-kubelet
+    testgrid-dashboards: sig-node-release-blocking
     testgrid-tab-name: kubelet-serial-gce-e2e-memory-manager
   labels:
     preset-service-account: "true"