bazel: stop tracking MODULE.bazel.lock

Set --lockfile_mode=off in .bazelrc, gitignore the file, and remove the
tracked copy.  Matches bazel-orfs's own .bazelrc:7.

Tracking the lockfile means every bazel-orfs / yosys / openroad bump
produces an 800k-line lock diff that buries the real coordinate change
under registry-entry churn (the previous yosys 0.63 bump in this branch
generated a 1456-line lock delta from a 4-line change in the resolved
yosys entry plus 728 lines of registry-fork residue).  We pin the
versions we care about explicitly in MODULE.bazel via BCR coordinates
and git_override(commit=…); the lockfile adds no integrity that those
pins don't already provide.

Signed-off-by: Øyvind Harboe <oyvind.harboe@zylin.com>

Author: oharboe

.bazelrc

@@ -1,3 +1,12 @@
 build --incompatible_strict_action_env
 build --cxxopt "-std=c++20" --host_cxxopt "-std=c++20"
+
+# Don't track MODULE.bazel.lock.  Resolved versions ride along with the
+# pinned BCR + git_override(commit=…) coordinates in MODULE.bazel and
+# downstream cache hits are what we actually care about.  Tracking the
+# lockfile just means every bazel-orfs / yosys / openroad bump produces
+# a 1000-line lock diff that buries the real change.  Matches what
+# bazel-orfs itself does (its own .bazelrc:7).
+common --lockfile_mode=off
+
 try-import %workspace%/user.bazelrc

.gitignore

@@ -102,6 +102,7 @@ bazel-bin
 bazel-out
 bazel-OpenROAD-flow-scripts
 bazel-testlogs
+MODULE.bazel.lock
 
 # python venv
 venv/