Previously, `gazelle` wouldn't look into `include`ed segments of module files when collecting the apparent to module name mapping.

* feat: gazelle_test test rule

* remove no_sandbox attr and add symlink check

* use readlink

* go_repository: add 'clean' build_file_generation

Before bzlmod, repositories were global, and BUILD files inside upstream
repositories could load from the repositories defined at the root-level
WORKSPACE file.

With the introduction of visibility rules, these result in errors that
cannot trivially be worked around. One pattern that has emerged is
ignoring existing build files by specifying `gazelle:build_file_name
BUILD.bazel`, however this does not work for anything already using
BUILD.bazel filenames.

This does affect real-world users: an example is
github.com/google/go-jsonnet which has a BUILD.bazel file to `genrule`
its AST. The module is pure-go, but the build step contains cpp code,
and when imported under bzlmod-gazelle will not work because the cpp
code is invoked. As a workaround, there is now a 'jsonnet' BCR module.

This patch introduces a `build_file_generation = clean` option, which
removes existing build files before generating new ones. It allows
loading the jsonnet code once again, and also makes it possible to
load some of the complex protobuf repositories.

* go_repository: always call fetch_repo, even for urls

After my changes to remove build files as part of fetch_repo, I realized
that when urls=[] is specified the code path doesn't use fetch_repo at
all. In this case, fetch_repo_args would remain None, and raise an
error. Not ideal!

This left me with two general options: either I move the code into a
separate command invocation, or I have all code go through fetch_repo.

The latter seems to be the pragmatic solution: gazelle by itself doesn't
generate code with urls=[] (in either bzlmod or vanilla update-repos),
so it's the option with lower performance impact (also considering we're
stacking it on top of a network download).

Also test compatibility of fetch_repo and gazelle.

* Remove reliance on specific canonical repo name scheme

Instead of relying on a particular separator char such as `~`, we instead only rely on the guaranteed fact that the apparent name of an extension repo is the last component of its canonical name.

Prepares for bazelbuild/bazel#22865

* Update go_repository_config.bzl

Builds ([example](https://buildkite.com/bazel/bazel-gazelle/builds/4022#01909d11-a3eb-4f13-bfd9-aa98755ba7d2)) are failing because this test is timing out on Mac OS.

Let's temporarily disable this large test to unblock development.

The `//internal:bazel_test` is still run on `ubuntu2204`

If two extensions both import Kinds from the same file, and no load
statement for those Kinds is already in the BUILD.bazel file, then
Gazelle will add the load statement twice.

In this commit, we fix the issue by updating the tracked loads when a
new load is inserted into the index. This will cause future iterations
to update the existing load instead of creating a duplicate.

…ching (#1845)

Prior to this commit, the regex for determining whether a file had
services did not require a space between the word "service" and the
service name. This could lead to false alarms, like "message
serviceABC". In this commit, we update the regex to only match if there
is at least one space between service and the service name.

When iterating on new language plugins, it is helpful to have the CheckFiles
validation run so that any mismatched BUILD file output can be shown.

Replacing `FailNow` with `Fail` allows for this

* Add ability to resolve label using regexp in directive resolve_regexp

* Add unit tests and update documentation

Fix formatting

Update test

Format test

remove extra whitespace

Trigger tests

Fix space

Also update `.bazelversion` to work around failures to fetch external repos.

…es (#1677)

This PR creates a tool that converts either a repository macro file or a WORKSPACE into a set of `go_deps.{}_overrides`. This is supposed to ease the migration to Bzlmod.

Fixes #1675

* prepare release 0.38

* Update MODULE.bazel