feat: harness VM stack (runner, measure-db, blackbox, Alloy, k6) and the 12 scenarios

Experiment design 5 and 7 for the harness VM (10.20.0.11): vm/harness/apply.sh pulls the secrets from Secret Manager,
compose runs runner:de076a7, measure-db, blackbox, Alloy (probe_success -> Mimir) and k6 under the campaign profile.
Scenario files C-K1..X-M2 are loaded by the runner. Harness ClusterRole gains replicasets get/list for rollout undo.

vm/harness/scenarios/X-M1.yaml

@@ -0,0 +1,28 @@
+# design 7 X-M1: misjudge probe, container. 25s partition api <-> db, just under the liveness failure window (3 x 10s);
+# observe whether kubelet restarts containers needlessly.
+id: X-M1
+path: misjudge
+asset: container
+expected_layer: 1
+ground_truth_label: transient_partition
+ground_truth_action: none
+description: NetworkChaos partition 25s, api -> 10.20.0.20
+inject:
+  method: chaos
+  manifest: |
+    apiVersion: chaos-mesh.org/v1alpha1
+    kind: NetworkChaos
+    metadata:
+      namespace: chaos-mesh
+    spec:
+      action: partition
+      mode: all
+      direction: to
+      externalTargets: ["10.20.0.20"]
+      selector:
+        namespaces: [demo]
+        labelSelectors:
+          app: api
+      duration: "25s"
+revert:
+  method: chaos_delete