Description of the problem / feature request:

The presence of a .bazelversion file that defines any non-matching version at the root of a directory structure prevents bazel from intepreting any commands in any subdirectory, including bazel version, help, info.

However, these are the commands needed to debug why .bazelversion is not satisfied, or to query non-build-related hel

We noticed that we have some common patterns for common conflicts/duplicate resolution in our monorepo across different binaries.
Like

  deploy_jar_rules=jar_rules(rules=[
    Duplicate('^BUILD', Duplicate.SKIP),
    Duplicate('^META-INF/ASL2.0', Duplicate.SKIP),
    Duplicate('^META-INF/INDEX.LIST', Duplicate.SKIP),
    Duplicate('^META-INF/io.netty.versions.properties', Duplicate.SKIP

One of the consumers of our system uses curly braces for content replacement in strings.

Due to the way that SD currently uses curly braces in the build process there is no way I can have a string that includes the braces for consumption.

I have tried a number of ways to escape the braces with no luck

Other languages and templating systems seem to use the concept of using double curly b

Bloop supports globs for source files since #1176.

The same should be done for resources.

Is your feature request related to a problem? Please describe.
Running any bazel build command on a fresh system with no Python, within a workspace that uses rules_haskell, will eventually yield an error of the form:

Repository rule _config_python3_toolchain defined at:
  /root/.cache/bazel/_bazel_root/abad448bf464eefeaf2734c3cc8cdd46/external/rules_haskell/haskell/ghc_bindist.bzl:59