[Doc] Improve rust analyzer section, distinguishing bzlmod and WORKSPACE

[bertulli]

The documentation for the rust-analyzer section is outdated, and realtive to the WORKSPACE approach. i tried improving it slightly, distinguishing the bzlmod approach. Right now, calling rust_analyzer_dependencies() when using bzlmod seems to throw an error. References issue #2997

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[UebelAndre]

Thanks! Just one question

[UebelAndre]

Is this accurate for bzlmod? I thought all the toolchains were registered by default for @rules_rust//tools/rust_analyzer:gen_rust_project (excluding the rust toolchain itself)

[bertulli]

i'm not sure i understood correctly (i'm not so experienced with bazel), but commenting the line register_toolchains("@rust_toolchains//:all") from MODULE.bazel made the project still build

[UebelAndre]

In other words, what should users expect to put in their MODULE.bazel files after reading this? Can you add a snippet for that?

[bertulli]

Thanks, i tried reducing the MODULE file as possible with the new features, now the only required part is one line, i pushed

[bertulli]

just to know, is there something i can do?

[UebelAndre]

Sorry this fell off my radar, back to you!

[UebelAndre]

In other words, what should users expect to put in their MODULE.bazel files after reading this? Can you add a snippet for that?

[UebelAndre]

Thank you!