Make load ignore modules marked as dev_dependency

[alextercete]

Description of the feature request:

load should ignore modules marked as dev_dependency for BUILD.bazel files not in the root module. If a public target depends (directly or indirectly) on such module, it should error with something like "target A depends on B, but B is marked as a dev dependency".

Which category does this issue belong to?

External Dependency

What underlying problem are you trying to solve with this feature?

Currently, you can't have public targets in the same BUILD.bazel file as you're loading a dev dependency:

# MODULE.bazel

bazel_dep(name = "bazel_skylib", version = "1.7.1", dev_dependency = True)

# BUILD.bazel

load("@bazel_skylib//rules:build_test.bzl", "build_test")

genrule(
    name = "genrule",
    outs = ["hello"],
    cmd = "echo world > $@",
    visibility = ["//visibility:public"],
)

build_test(
    name = "test",
    targets = [":genrule"],
)

When trying to use :genrule from another module, you get an error saying the dev dependency can't be found:

ERROR: error loading package '@@b~//': Unable to find package for @@[unknown repo 'bazel_skylib' requested from @@b~]//rules:build_test.bzl: The repository '@@[unknown repo 'bazel_skylib' requested from @@b~]' could not be resolved: No repository visible as '@bazel_skylib' from repository '@@b~'.
ERROR: /home/aleter01/Sandbox/dev_dependency/BUILD.bazel:1:6: error loading package '@@b~//': Unable to find package for @@[unknown repo 'bazel_skylib' requested from @@b~]//rules:build_test.bzl: The repository '@@[unknown repo 'bazel_skylib' requested from @@b~]' could not be resolved: No repository visible as '@bazel_skylib' from repository '@@b~'. and referenced by '//:genrule'

Which operating system are you running Bazel on?

Linux

What is the output of bazel info release?

release 7.4.0

If bazel info release returns development version or (@non-git), tell us how you built Bazel.

No response

What's the output of git remote get-url origin; git rev-parse HEAD ?

Have you found anything relevant by searching the web?

No, but I've asked about this in the Bazel Slack.

Any other information, logs, or outputs that you want to share?

Here's a reproduction of the current behaviour. The current workaround seem to be to split targets which depend on the dev dependency into a separate BUILD.bazel file.

[fmeum]

This would require being able to evaluate BUILD files without having resolved all loads, which isn't easy in the current module.

CC @brandjon @comius for "lazy load"