Add two more options to `bazel mod show_repo` that allow showing "all" repos, for some definition of "all":

* `--all_repos` actually shows all repos in the workspace;
* `--all_visible_repos` shows all repos visible to the `--base_module`, accompanied by the apparent repo name each repo is known by.

These two options provide a replacement for `bazel query //external:*` that used to work in the WORKSPACE era.

A few notes:

1.  Technically, `--all_visible_repos` is possible already using something like
    ```sh
    bazel mod dump_repo_mapping '' |
        jq -r 'to_entries[] | select(.value != "" and .value != "bazel_tools") | "@" + .key' |
        xargs bazel mod show_repo
    ```
    However, that's clearly too complicated for everyone using Bazel to construct on their own. `dump_repo_mapping` is also not documented on the Bazel website.

    I am unable to come up with a way to get the same effect as `--all_repos` with existing commands.

2.  Related to `--all_visible_repo`: I considered creating a `--base_repo` option so that one can examine all repos visible to a module extension repo, but decided against it:

    * It's unclear how `--base_repo` should interact with `--base_module` – or if they should be the same option in the first place.
    * It makes this PR a little too complicated. (We'd either need another call to Skyframe to get the repo mapping since it's not available in moduleInspector or depGraphValue, or inline the logic in [ModuleExtensionRepoMappingEntriesFunction](https://cs.opensource.google/bazel/bazel/+/master:src/main/java/com/google/devtools/build/lib/bazel/bzlmod/ModuleExtensionRepoMappingEntriesFunction.java;l=75-77;drc=c475b38401d80dc4970ddc7ac18b4d74e0eacac3) into ModCommand).

Fixes: bazelbuild#27224

Closes bazelbuild#27241.

PiperOrigin-RevId: 825976519
Change-Id: I5d8cf1cf584a7e167173cf3ba3725fffc0fd5299

…s` (#28012)

Add two more options to `bazel mod show_repo` that allow showing "all"
repos, for some definition of "all":

* `--all_repos` actually shows all repos in the workspace;
* `--all_visible_repos` shows all repos visible to the `--base_module`,
accompanied by the apparent repo name each repo is known by.

These two options provide a replacement for `bazel query //external:*`
that used to work in the WORKSPACE era.

A few notes:

1. Technically, `--all_visible_repos` is possible already using
something like
    ```sh
    bazel mod dump_repo_mapping '' |
jq -r 'to_entries[] | select(.value != "" and .value != "bazel_tools") |
"@" + .key' |
        xargs bazel mod show_repo
    ```
However, that's clearly too complicated for everyone using Bazel to
construct on their own. `dump_repo_mapping` is also not documented on
the Bazel website.

I am unable to come up with a way to get the same effect as
`--all_repos` with existing commands.

2. Related to `--all_visible_repo`: I considered creating a
`--base_repo` option so that one can examine all repos visible to a
module extension repo, but decided against it:

* It's unclear how `--base_repo` should interact with `--base_module` –
or if they should be the same option in the first place.
* It makes this PR a little too complicated. (We'd either need another
call to Skyframe to get the repo mapping since it's not available in
moduleInspector or depGraphValue, or inline the logic in
[ModuleExtensionRepoMappingEntriesFunction](https://cs.opensource.google/bazel/bazel/+/master:src/main/java/com/google/devtools/build/lib/bazel/bzlmod/ModuleExtensionRepoMappingEntriesFunction.java;l=75-77;drc=c475b38401d80dc4970ddc7ac18b4d74e0eacac3)
into ModCommand).

Fixes: #27224

Closes #27241.

PiperOrigin-RevId: 825976519
Change-Id: I5d8cf1cf584a7e167173cf3ba3725fffc0fd5299

Commit
b292706

---------

Co-authored-by: Timothy Gu <[email protected]>
Co-authored-by: Yun Peng <[email protected]>