Gauging interest in a PR that lets a user add additional bats libraries

[leviable]

I've been working on a patch to bazel-bats that lets a user include additional bats libraries via their MODULE.bazel. The API for the end user would look something like this:

bazel_dep(name = "bazel_bats", version = "0.38.9")

bazel_bats = use_extension("@bazel_bats//:extensions.bzl", "bazel_bats_deps")
bazel_bats.bats_lib(
    name = "bats-file",
    version = "0.4.0",
    sha256 = "9b69043241f3af1c2d251f89b4fcafa5df3f05e97b89db18d7c9bdf5731bb27a",
)
bazel_bats.bats_lib(
    name = "bats-mock",
    version = "2.2.0",
    sha256 = "a997ebc190cdc9d5a08a51a9f7a6ddd54999bf9a0fcc899b1ae739ba12a90216",
    github_org = "buildkite-plugins",
)

use_repo(
    bazel_bats,
    "bats_core",
    "bats_support",
    "bats_assert",
    "bats_file",
    "bats_mock",
)

Would you be interested in a PR to add that functionality? If so, what would be your conditions and/or restrictions?

[filmil]

Hi! As for rules and regulations, this is an individual's repo (mine) with a known LICENSE, so for now, just being reasonable and agreeable is hopefully enough. :)

That said, is there a reason why this functionality should be part of bazel-bats, vs simply imported via the regular repo rules, or a stand-alone module? It does not seem that beyond making the repos available this offers anything else in terms of rules do I see it correctly?

Here's why I ask: I discovered that BCR modules work best if they are small and focused. I might not be able to follow bats development, so if you have a way to make these libraries an independent module, you might end up being happier long term.

This is not to say I'm not open to accepting the contribution, but I would like to know a good reason why this is in your opinion a better way forward vs any alternative. Happy to accept an answer.