Disable lockfile check for BCR test module

Enforcing an up-to-date lockfile made contributions more complicated.

.bazelci/presubmit.yml

@@ -26,19 +26,6 @@ tasks:
     - rm pkg/BUILD.bazel
     - bazel run //:gazelle -- update pkg
     - bazel run //:gazelle -- pkg
-    build_flags:
-    # Verify that the committed lockfile is platform-independent.
-    # In case of expected changes, regenerate the lockfile with
-    # `bazel mod graph`, which evaluates all module extensions.
-    # Note: `go_sdk`s *is* platform-dependent since it registers the first
-    # host-compatible SDK, but the result only differs if there is also a
-    # matching SDK with manual goos/goarch set, which isn't the case in CI.
-    # TODO: Make this more realistic after
-    # https://github.com/bazelbuild/bazel/issues/19154.
-    - "--lockfile_mode=error"
-    test_flags:
-    # See above.
-    - "--lockfile_mode=error"
     build_targets:
     - "//..."
     - "//:gazelle"

.gitignore

@@ -6,5 +6,6 @@
 /tests/bcr/bazel-bin
 /tests/bcr/bazel-out
 /tests/bcr/bazel-testlogs
+/tests/bcr/MODULE.bazel.lock
 .DS_STORE
 .ijwb/