[CI] Adjust CPU and memory limits

After switching to n2-highcpu-32 machines, the CPU and memory
requests/limits were left at the same values. This led to pods not
being scheduled or failing due to running out of memory relative to
the requests.

This patch updates the values to reflect the actual machine shapes
that we are running on.

Author: boomanaiden154

premerge/linux_container_pod_template.yaml

@@ -20,7 +20,7 @@ spec:
       # It's not used for scheduling, but can be used by k8 for OOM kill.
       requests:
         cpu: "100m"
-        memory: "50Gi"
+        memory: "25Gi"
       limits:
-        cpu: 56
-        memory: "100Gi"
+        cpu: 32
+        memory: "32Gi"

premerge/linux_runners_values.yaml

@@ -47,10 +47,10 @@ template:
         # itself doesn't need much, just using something enough not to get
         # OOM killed.
         requests:
-          cpu: 50
+          cpu: 25
           memory: "2Gi"
         limits:
-          cpu: 56
+          cpu: 32
           memory: "2Gi"
       env:
         - name: ACTIONS_RUNNER_CONTAINER_HOOKS

premerge/windows_runner_values.yaml

@@ -21,7 +21,7 @@ template:
       - name: runner
         resources:
           requests:
-            cpu: 50
+            cpu: 25
         # TODO(boomanaiden154): Update this image when we have a proper windows
         # image ready.
         image: ghcr.io/keenuts-test-org/windows-ci-image:latest