Cyclic dependencies when generating rust-project.json

[UebelAndre]

Hi 👋

I'm hopeful someone here will have some context that can help. For Bazel, we have a tool that generates rust-project.json from Bazel targets but we discovered a bug that creates cyclic dependency graph for test dependencies. Does anyone know what the expected behavior is in rust-analyzer? Should we be supporting cyclic trees like this? What is the behavior with Cargo.toml files? Any info would be helpful!

• Infinite cycle in rust-analyzer caused by test deps bazelbuild/rules_rust#2488

Thanks!