Run bazel jobs on 4xlarge (#92340)
After the previous fix to limit the CPU and memory used by Bazel, I see one case today where the runner runs out of memory in a "proper" way with exit code 137 https://hud.pytorch.org/pytorch/pytorch/commit/0c8f4b58934cbfe4a52d261c914ff8b2632c4f5c. So, the memory usage must be close to limit of an 2xlarge instance. It makes sense to preemptively use 4xlarge now (like XLA)
Pull Request resolved: https://github.com/pytorch/pytorch/pull/92340
Approved by: https://github.com/clee2000
