Summary

Upgrades this repo to build under Bazel 9.2.0 and pins the prebuilt rules_minidock_tools binaries (merge-app, puller-app, pusher-app) to the latest release, v0.0.77.

Changes

• Bazel 9.2.0 compatibility: Bazel 9 removed the implicit/native symbols this repo relied on.
  • minidock/container_binary.bzl now explicitly loads java_common from @rules_java//java/common:java_common.bzl instead of relying on the native global.
  • minidock/container_data_tools/BUILD now explicitly loads py_binary from @rules_python//python:defs.bzl.
  • rules_java and rules_python are declared as regular (non-dev) bazel_deps in MODULE.bazel since the above loads are needed outside of tests.
  • MODULE.bazel.lock regenerated for the dependency graph changes.
• multitool.lock.json bump: merge-app/puller-app/pusher-app pinned from v0.0.75 to v0.0.77 across all platforms (linux-x86_64, macos-aarch64, macos-x86_64), URLs and sha256 hashes updated to match the v0.0.77 release assets.
  • v0.0.77 includes a fix (bazeltools/rules_minidock_tools#649) for a puller-app bug where pulling from gcr.io failed with Invalid auth header — gcr.io returns its WWW-Authenticate challenge with an unquoted service value, which the old header parser didn't handle.

Test plan

• ./bazel clean --expunge && ./bazel build //tests/simple_flow:test_simple_imagen succeeds from a cold cache, confirming Bazel 9.2.0 resolves the new deps and fetches/uses the v0.0.77 binaries (verified the fetched puller-app sha256 matches the pinned lockfile entry via the content-addressable repo cache).