chore: upgrade bazel → 7.0.0

- fix: drop flags eliminated during release
- chore: upgrade `rules_java` → `7.1.0`
- chore: upgrade `rules_cc` → `0.0.9`
- chore: upgrade all local bazel v7 versions to stable `7.0.0`

Signed-off-by: Sam Gammon <sam@elide.ventures>

.bazelci/presubmit.yml

@@ -1,6 +1,6 @@
 ---
 matrix:
-  bazel_version: ["6.3.2", "7.0.0-pre.20230816.3"]
+  bazel_version: ["6.3.2", "7.0.0"]
   platform: ["centos7", "debian10", "macos", "ubuntu2004"]
 
 validate_config: 1

.bazelversion

@@ -1 +1 @@
-7.0.0-pre.20230816.3
+7.0.0

.github/CONTRIBUTING.md

@@ -16,7 +16,7 @@ Both of these clients use the `.bazelversion` file to determine what version of
 ```
 ➜  rules_graalvm git:(main) cat .bazelversion
 
-7.0.0-pre.20230816.3
+7.0.0
 ```
 
 Once you have Aspect, Bazelisk, or _that exact Bazel binary version_ installed and ready to go, you can proceed.

.github/workflows/module.build.yml

@@ -38,7 +38,7 @@ name: "Build"
       bazel_version:
         description: "Bazel version"
         type: string
-        default: "7.0.0-pre.20230816.3"
+        default: "7.0.0"
 
       ## Configuration profile to use
       bazel_config:
@@ -77,7 +77,7 @@ name: "Build"
       bazel_version:
         description: "Bazel version"
         type: string
-        default: "7.0.0-pre.20230816.3"
+        default: "7.0.0"
       bazel_config:
         description: "Bazel profile"
         type: string

BUILD.bazel

@@ -18,8 +18,6 @@ load(
         "python_requirements",
         "buildifier.check",
         "buildifier.format",
-        "generator",
-        "generator.update",
     ]
 ]
 

MODULE.bazel

@@ -36,7 +36,7 @@ bazel_dep(
 )
 bazel_dep(
     name = "rules_java",
-    version = "6.4.0",
+    version = "7.1.0",
 )
 bazel_dep(
     name = "bazel_skylib",
@@ -59,7 +59,7 @@ bazel_dep(
 )
 bazel_dep(
     name = "rules_cc",
-    version = "0.0.8",
+    version = "0.0.9",
     dev_dependency = True,
 )
 bazel_dep(