This makes it possible to load gazelle under any repo name, not
necessarily bazel_gazelle. This opens up the possibility to call the
gazelle Bazel module "gazelle".

* Prototype of bzlmod-powered transitive dependencies

Modules can use the `go_deps` module extension to define Go dependencies.

Only Go module dependencies are supported for now (`go_deps.module`).

HTTP and VCS Go repositories can be implemented for the root module only
using the new bazel_module.is_root field added in
bazelbuild/bazel#15792 has been merged. They
should follow the semantics of archive_override/git_override.

* Update internal/bzlmod/go_deps.bzl

Co-authored-by: Zhongpeng Lin <zplin@uber.com>

Co-authored-by: Zhongpeng Lin <zplin@uber.com>

Since bazelbuild/bazel@263c24e,
repositories created by modules and module extensions must have names
that start with a letter - underscores are no longer allowed.

Previously, such errors would lead to the following error message:

```
gazelle: json: cannot unmarshal object into Go struct field moduleFromList.Error of type string
```

This is fixed by changing the definition of the `Error` field to be an
object with an Err field of type string, as described at:
https://go.dev/ref/mod#go-list-m

Also fixes an incorrect test stub.

* bzlmod: Rename go_deps.module importpath parameter to path

Go itself calls this a "module path" rather than an "import path" - it
will rarely be a valid import path anyway.

* bzlmod: Add a go.mod/go.sum parser

* bzlmod: Add go_deps.from_file

With go_deps.from_file, dependencies can be parsed from a go.mod/go.sum
pair directly by the go_deps module extension. Users only have to
declare visibility for their *direct* dependencies in their
MODULE.bazel.

* bzlmod: Make go mod and gazelle ignore tests/bcr/

In order to help folks extend Gazelle quicker and easier, provide a base
implementation of the language.Language interface where everything is
no-ops.

End users then can simply compose their downstream struct with this
to have a valid implementation to iterate upon.

This allows supporting patterns like `maybe`, which take a
rule-to-instantiate as a positional argument.

This allows languages to configure their Kinds/Loads calls based on
command line flags.

Closes #1274
Fixes #1275

Necessary after bazelbuild/bazel@7f9de9e

Also switches the Bazel version to last_green to learn of new potential
breakages faster.

… directive (#1326)

Since #1310 we can add
arguments to rules - this PR allows symbols to be loaded for these
arguments.

This is required to allow repositories generated for Go modules to see
proto_library.

Work towards bazel-contrib/rules_go#3265

Co-authored-by: Tyler French <66684063+tfrench-uber@users.noreply.github.com>