prepare release 0.30 (bazelbuild#1486)

adding go version and std_package_list to releaser (bazelbuild#1415)

Update dependencies per pre-release process (bazelbuild#1357)

bzlmod: Add support for custom `go_proto_library` compilers (bazelbui…

…ld#1348)

These changes are required to allow users of `rules_go` to use all the
custom `go_proto_library` compilers defined in its `//proto` package
**if they provide their own definitions of them**:
* Make `gazelle` and `protobuf` visible to `go_repository` targets under
  their legacy `WORKSPACE` names.
* Expose `build_file_proto_mode` on `go_deps.module`.

bzlmod: Simplify go_grpc_library support (bazelbuild#1346)

Also raise the module version to match the latest release.

release new version of gazelle (bazelbuild#1323)

Co-authored-by: Tyler French <[email protected]>

bzlmod: Depend on rules_proto (bazelbuild#1331)

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

Work towards bazelbuild/rules_go#3265

bzlmod: Fix canonical label literal after Bazel change (bazelbuild#1322)

Necessary after bazelbuild/bazel@7f9de9e

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

bzlmod: Add go_deps.from_file (bazelbuild#1300)

* 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/

bzlmod: Do not create a repository with an invalid name (bazelbuild#1304

)

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