test/e2e: increase memory limits in pod resize tests

The pod resize e2e tests use memory limits as low as 20Mi for Guaranteed
QoS pods. On OpenShift/CRI-O, the container runtime (runc) runs inside
the pod's cgroup and requires ~20-22MB of memory during container
creation and restart operations. This causes intermittent OOM kills
when the pod's memory limit is at or below runc's memory footprint.

This issue does not occur on containerd-based clusters because
containerd's shim runs outside the pod's cgroup by default (ShimCgroup=""),
so runc's memory is not charged against the pod's limit.

Increase memory limits to provide sufficient headroom for runc:
- originalMem: 20Mi -> 35Mi
- reducedMem: 15Mi -> 30Mi
- increasedMem: 25Mi -> 40Mi

The test validates resize behavior, not minimal memory limits, so
larger values do not reduce test coverage.

Signed-off-by: Damien Grisonnet <dgrisonn@redhat.com>

test/e2e/common/node/pod_resize.go

@@ -51,12 +51,12 @@ const (
 	increasedCPU      = "25m"
 	increasedCPULimit = "35m"
 
-	originalMem       = "20Mi"
-	originalMemLimit  = "30Mi"
-	reducedMem        = "15Mi"
-	reducedMemLimit   = "25Mi"
-	increasedMem      = "25Mi"
-	increasedMemLimit = "35Mi"
+	originalMem       = "35Mi"
+	originalMemLimit  = "45Mi"
+	reducedMem        = "30Mi"
+	reducedMemLimit   = "40Mi"
+	increasedMem      = "40Mi"
+	increasedMemLimit = "50Mi"
 )
 
 func offsetCPU(index int, value string) string {