Migration to bazelmod/Bazel 8

[stridge-tnp]

This is a draft of migration to bazel 8 and away from WORKSPACE. Its based on the branch @hovind made that i have modified slightly.

Relevant issues: #336 #210
Revelant PRs: bazelbuild/bazel-central-registry#4341

.bazelrc config

common --registry=https://raw.githubusercontent.com/UebelAndre/bazel-central-registry/verilator

MODULE.bazel snippet

bazel_dep(name = "rules_hdl", version = "")
git_override(
    module_name = "rules_hdl",
    commit = "34c35fe03f06d7f7ded79a36e54d73415fc12595",
    remote = "https://github.com/TernaryNP/bazel_rules_hdl.git",
)

bazel_dep(name = "verilator", version = "5.034")

I have verified that verilator is working correctly with these changes. Maybe someone can take over from here and ensure other parts of bazel_rules_hdl are not broken.
@hovind @UebelAndre @QuantamHD

[UebelAndre]

I will likely continue to try get equivalents to what's in @rules_hdl//dependency_support as granular BCR modules before trying to tackle any rules_hdl rules. That's an area I could use some support as I don't have a use case for everything that's in there. I don't think rules_hdl should care about how things are built, it should just be the rules that wrap various tools so if the logic for building the dependencies can be separated, I think the rules themselves become more standardized. Do you wanna collaborate on getting more of the dependencies into BCR?

[stridge-tnp]

I am mainly an fpga person. I can help with verilator/vivado sections of this as I added them. Anything outside that will have to be someone else.

You have done verilator already, so I can help/test Vivado. It's a bit annoying bc you need the expensive license.