Fix dev QA script

[maggie-lou]

• Disable bzlmod on builds (and remove bazel repo build because it's been fully migrated to bzlmod, and we haven't done enough testing to guarantee our toolchain work well with bzlmod)
• Fail script if a QA build fails
• Add API key to builds
• Update to the latest buildbuddy toolchain

Related issues: Fixes https://github.com/buildbuddy-io/buildbuddy-internal/issues/3167

[maggie-lou]

• Fix dev QA script #6092 👈
• master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @maggie-lou and the rest of your teammates on Graphite

[bduffany]

nit: instead of removing bazel we could also pin at a known good commit and bazel version. I think in general we probably want to pin all of these to a known good commit (plus a bazel version if a .bazelversion is missing from the repo), so that if these repos break then we don't have to block the release

[maggie-lou]

Done - pinned all the commit shas to current HEAD. For the bazel repo, pinned to the parent commit before they cleared their WORKSPACE file. Also pinned bazel version to 7.0.2

Was going back and forth on whether we should pin the bazel version, because we might want to know if builds are breaking on a later bazel version. But I think pinning it will make things more stable, and we can find that out other ways

[maggie-lou]

I'm actually having trouble getting bazel repo to build on an older commit. I want to make sure these fixes get in before the next release, so just going to remove bazel for now. We'll still have a go, c++, and python test build

[bduffany]

LGTM (we can maybe pin these to known good commits another time, since that seems like it might be slightly tricky when using the github checkout action)