test(e2e): match the guest-console-log assertion to the Phase 2 KubernetesNodes CR

Since the Phase 2 split the e2e worker pool is a separate KubernetesNodes CR
whose fields sit two spaces under spec, not six spaces under a nodeGroups.<name>
block, so the logSerialConsole assertion is re-anchored to the two-space key.

Signed-off-by: IvanHunters <xorokhotnikov@gmail.com>

hack/run-kubernetes-serial-console_test.bats

@@ -1009,9 +1009,11 @@ run_capture() {
 }
 
 @test "the e2e tenant node group asks KubeVirt for the guest console log" {
-  # Anchored to a bare six-space-indented key so a comment or a prose mention
-  # of the field cannot stand in for the setting itself. It does not prove the
-  # key sits in the nodeGroups block specifically -- the render is what would
-  # catch that, and the chart's own suites cover it.
-  grep -q '^      logSerialConsole: true$' hack/e2e-chainsaw/_lib/run-kubernetes.sh
+  # Anchored to a bare two-space-indented key so a comment or a prose mention
+  # of the field cannot stand in for the setting itself. Since the Phase 2 split
+  # the worker pool is a separate KubernetesNodes CR whose fields sit two spaces
+  # under spec, not six spaces under a nodeGroups.<name> block. It does not prove
+  # the key sits in that CR specifically -- the render is what would catch that,
+  # and the chart's own suites cover it.
+  grep -q '^  logSerialConsole: true$' hack/e2e-chainsaw/_lib/run-kubernetes.sh
 }