fix(ci): lower aarch64 benchmark memory request to 128Gi cluster limit

[jbachorik]

What does this PR do?:
Lowers KUBERNETES_MEMORY_REQUEST and KUBERNETES_MEMORY_LIMIT for benchmarks-candidate-aarch64 from 200Gi to 128Gi.

Motivation:
All benchmark jobs are failing with:

Preparation failed: MemoryRequest of 200Gi exceeds the allowed limit of 128Gi.

The 200Gi value was carried over from the original CI migration and presumably reflected the old cluster's limits. The arm64 runner pool now enforces a 128Gi cap.

Additional Notes:
The amd64 job has no explicit memory override so it is unaffected.

How to test the change?:
Benchmark jobs should no longer fail at preparation. No functional change to benchmark behaviour.

For Datadog employees:

• This PR doesn't touch any of that.
• JIRA: N/A

[dd-octo-sts]

CI Test Results

Run: #27755064362 | Commit: 3da466e | Duration: 14m 38s (longest job)

✅ All 32 test jobs passed

Status Overview

JDK	glibc-aarch64/debug	glibc-amd64/debug	musl-aarch64/debug	musl-amd64/debug
8	-	✅	-	-
8-ibm	-	✅	-	-
8-j9	✅	✅	-	-
8-librca	-	-	✅	✅
8-orcl	-	✅	-	-
11	-	✅	-	-
11-j9	✅	✅	-	-
11-librca	-	-	✅	✅
17	✅	✅	-	-
17-graal	✅	✅	-	-
17-j9	✅	✅	-	-
17-librca	-	-	✅	✅
21	✅	✅	-	-
21-graal	✅	✅	-	-
21-librca	-	-	✅	✅
25	✅	✅	-	-
25-graal	✅	✅	-	-
25-librca	-	-	✅	✅

Legend: ✅ passed | ❌ failed | ⚪ skipped | 🚫 cancelled

Summary: Total: 32 | Passed: 32 | Failed: 0

---

Updated: 2026-06-18 11:21:29 UTC

[datadog-datadog-prod-us1-2]

✨ Fix all issues with BitsAI

⚠️ Warnings

🚦 14 Pipeline jobs failed

DataDog/java-profiler | benchmarks-candidate-aarch64: [alloc]     

DataDog/java-profiler | benchmarks-candidate-aarch64: [cpu,wall,alloc,memleak]     

DataDog/java-profiler | benchmarks-candidate-aarch64: [cpu,wall]     

View all 14 failed jobs.

Useful? React with 👍 / 👎

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 27e7e01 | Docs | Datadog PR Page | Give us feedback!}

[jbachorik]

This needs to be fixed differently.