OOM Guard Retry Logic Has Broken Bazel Flag Syntax

Problem

When any Bazel command fails, the OOM guard retry logic in `bazel_evergreen_shutils.sh` attempts to retry with invalid flag syntax: `--local_resources=HOST_CPUS*.5`

Bazel rejects this with: "Variable definitions must be in the form of a 'name=value' assignment"

The retry fails, but the wrapper script's CI fallback logic causes the task to report SUCCESS, masking the actual build failure.

Impact

• Failed Bazel builds are silently reported as successful
• Makes debugging build failures difficult
• Test tasks fail later with missing artifacts instead of failing at compile time