Delete .bazelrc now that Bazel 7 is released

[cpsauer]

bzlmod is now enabled by default. Follows up on #412, cleaning things up :)

(Hopefully the GitHub images have been updated to 7.0 and the tests will pass. If not, maybe rerun in a month--still worth my posting the PR, I think, so we don't forget to do this cleanup at some point.)

Cheers,
Chris

[cpsauer]

The images do indeed have Bazel 7 (looks like they use Bazelisk), so this is safe to merge on its own.

...but the build breakages are other Bazel 7-related issues, it looks like, that would break with HEAD w/ no code changes.
Not sure what's going on there. Bazel 7 should auto detect...perhaps a bug by them there.

Could be worth adding a .bazelversion file and having renovate auto-update? That way Bazel would always be on a working version.

[cpsauer]

Have filed underlying issue over at bazelbuild/bazel#20537

[cpsauer]

And worked around incompatible changes.

Lmk if you want help getting renovate to manage moving between bazel versions, so you never get silently broken by a Bazel update again.

Sketch: Just add a .bazelversion file pointing to a specific version and Renovate will pick it up. I'd advise using rolling (currently 8.0.0-pre.20231030.2) to hit issues before users like rules_apple does, and setting up auto updates so you don't go nuts having to approve a PR for a new bazel rolling version every week or two. In terms of Renovate config, you'd enable automatic merging for green builds as in #411 (comment), and let it track Bazel rolling (instead of normal releases) via

{
    "description": "Use rolling pre-releases for bazel itself.",
    "matchManagers": ["bazelisk"],
    "ignoreUnstable": false,
  }

[thomasvl]

Thanks!