feature request - upstream all feature requirements of bazel-orfs scala_ commands and retire bazel-orfs scala_ commands

[oharboe]

bazel-orfs contains various odds and ends which really should be handled upstream in more specialized repositories, such as use https://registry.bazel.build/modules/rules_scala directly.

bazel-orfs has implemented its own scala_* rules while figuring out what it takes to make Chisel work well.

[oharboe]

@MrAMS FYI, you fixed a major example of this by moving verilator to bazel bcr. Thank you!

[MrAMS]

Related issue rules_scala/issues/915, we may wait for upstream.

[oharboe]

I haven't tried bazelbsp in Metals for a while, nor do I know exactly how to configure scala and Chisel to use bazelbsp, but last time it locked up bazel on the command line, but now there's a way to use a separate bazel bsp server for the GUI for the vscode bazel plugin and the command line shell https://github.com/bazel-contrib/vscode-bazel?tab=readme-ov-file#configuring-the-extension. Perhaps there's a path forward for Metals and Chisel support?

[MrAMS]

I also faced problem when using zed-metals. Maybe it will be fixed when we use BCR rules_scala. I am working on it now.

[MrAMS]

check new PR The-OpenROAD-Project/bazel-orfs/pull/453

[oharboe]

@MrAMS Fixed