[Doc] Clean up the bzlmod approach as much as possible

Author: bertulli

docs/rust_analyzer.vm

@@ -10,15 +10,12 @@ such a file.
 
 #### Bzlmod
 
-First, ensure `rules_rust` is setup in your workspace. By default, `rust_register_toolchains` will
-ensure a [rust_analyzer_toolchain](#rust_analyzer_toolchain) is registered within the WORKSPACE.
-
-Next, load the dependencies for the `rust-project.json` generator tool:
+First, ensure `rules_rust` is setup in your workspace:
 
 ```python
-# BUILD.bazel
+# MODULE.bazel
 
-load("@rules_rust//tools/rust_analyzer:deps.bzl", "rust_analyzer_dependencies")
+bazel_dep(name = "rules_rust", version = "0.59.2")
 ```
 
 Bazel will create the target `@rules_rust//tools/rust_analyzer:gen_rust_project`, which you can build
@@ -35,7 +32,8 @@ rust-analyzer can pick it up upon restart.
 
 #### WORKSPACE
 
-As with Bzlmod, ensure `rules_rust` is setup in your workspace.
+Alternatively, you can use the legacy WORKSPACE approach. As with Bzlmod, ensure `rules_rust` is
+setup in your workspace.
 
 Moreover, when loading the dependencies for the tool, you should call the function `rust_analyzer_dependencies()`: